Yet another way, and I apologise if someone already said this and I missed
it, but I have one common binding directory for building programs, but for
service programs I create a separate binding directory for each one that
only contains what is necessary to build that service program. The service
program binding directory is named the same as the service program.
On Feb 5, 2018 11:56 AM, "Craig Richards" <craig@xxxxxxxxxxxxxxxx> 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
--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
https://archive.midrange.com/rpg400-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link:
http://amzn.to/2dEadiD
midrange.com
