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



Craig,

I also found this situation frustrating. It would be nice if there was some sort of default and maybe a *BNDDIR designation as to priority. Normally I would want the program to reference the *SRVPGM export.

I just have separate binding directories for the service program and programs referencing the service program. That solves the problem nicely.

-mark

On 2/5/2018 11:56 AM, Craig Richards wrote:
Hi All,

Having worked so long, using particular standards at a couple of sites, I
find myself going back to re-address some of the ways things were set up so
many years ago...

When recreating Service Programs which reference binding directories in
which the Service Program already exists...

You get the error: "Definition supplied multiple times for..." because the
same subprocedures exist in the module for the service program you are
recreating and in the Service Program itself referenced in the binding
directory.

It seemed to me that there were two ways to solve this problem:

1. Take the Service Program out of the binding directory while you
re-create it, then put it back.
2. Specify Option(*DupProc) on the Create Command.

I always chose the latter of these, but neither seems ideal.

Am I missing something obvious? Has anyone got a better solution?

Thanks and regards as always,
Craig

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.