Re: Serviceprogram and BNDDIR Parameter

Simon,

Bad coffee this morning? Strong words you start out with.

If you read Alexander's post, he does NOT want to specify *DupProc. He
feels it's as evil as it is.

Alexander, simply remove service program S1 from the binding directory
before recreating it and your problem will go away.

Gary Guthrie
Senior Technical Editor, iSeries NEWS


Simon Coulter wrote:
>
> Hello Alexander,
>
> You wrote:
> >When we try to create the service program I get the error:
> >CPD5D03:  Definition supplied multiple times for symbol ....
>
> Let me know if you want an explanation of why this is occurring.
>
> >How can we solve this problem?
>
> This question is identical to the following:  "Doctor, my arm hurts when I
> do this."  The only possible answer is: "Well, don't do that!"
>
> Using a SINGLE binding directory for everything is stupid.  You must
> analyse your dependencies and create appropriate binding directories.  I
> generally specify the list of modules and service programs when creating
> service programs.  I generally use binding directories when building
> programs.  I would not put a module used by a service program in a binding
> directory used to create programs.
>
> >If we set the parameter OPTIONS in the CRTSRVPGM or
> >UPDSRVPGM command to *DUPPROC the program is then
> >created without error. But it makes it impossible to defend
> >against problems caused by someone creating a completely
> >different procedure with the same name as another.
>
> *DUPPROC and *DUPVAR are kludgy work-arounds to compensate for bad design.
> You should not be exporting multiple procedures or multiple variables with
> the same name.
>
> Regards,
> Simon Coulter.