Re: 2 same named procedures in 2 separate service programs creating problems

[Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx>]

+10 upvotes, Alan.

I have a naming convention and I use it for all my service programs.  
Now I still show my midrange roots in that the identifying key is a 
three-letter acronym, but there's a method to my madness.  I name the 
service program SPXXX, and I name all the modules SPXXXMMM, and then I 
create the service program using MODULES(SPXXX*).  Works like a charm.

Then, all of my procedures start with XXX_.  Not a whole lot of extra 
typing, and there's a consistency throughout the architecture.


On 5/22/2019 5:02 PM, Alan Campin wrote:
> This is why I have been saying for twenty years. Put the name of the
> service program on the front of each procedure so you know were it come
> from and to avoid clashes.
>
> I don't know if anyway to fix it except going through the service program
> and renaming or adding the service program name on the front and going
> through and changing everyplace it is used.
>
>
>
> On Wed, May 22, 2019 at 2:21 PM Alan Shore via MIDRANGE-L <
> midrange-l@xxxxxxxxxxxxxxxxxx> wrote:
>
> > Hi everyone
> > Before I forget - we are on V7r3
> >
> > We have someone needing to make a change to a program that hasn't been
> > changed in quite some time
> > The first step that was taken - was to obtain the program from production,
> > into our development system - and compile it
> > It did not compile
> > The investigation shows that we have 2 procedures with the same name in 2
> > separate service programs, each in different binding directories
> > We have tried removing the binding directories one at a time - but the
> > program doesn't compile
> > Is there any way to bypass this situation with the source for compiling
> > I tried Google searches - but to no avail
> >
> > As always - any and all help gratefully accewpted
> >
> > Alan Shore
> > E-mail : ASHORE@xxxxxxxx
> > Phone [O] : (631) 200-5019
> > Phone [C] : (631) 880-8640
> > 'If you're going through hell, keep going.'
> > Winston Churchill
> >
> > --
> > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> > To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
> > To subscribe, unsubscribe, or change list options,
> > visit: https://lists.midrange.com/mailman/listinfo/midrange-l
> > or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
> > Before posting, please take a moment to review the archives
> > at https://archive.midrange.com/midrange-l.
> >
> > Please contact support@xxxxxxxxxxxx for any subscription related
> > questions.
> >
> > Help support midrange.com by shopping at amazon.com with our affiliate
> > link: https://amazon.midrange.com