Re: 2 same named procedures in 2 separate service programs

[Paul Bailey <PabloMotte+Midrange@xxxxxxxxx>]

One of the tools in Craig Rutledge's suite of Open Source iSeries Tools
(JCRCMDS) is named JCRBND and that lists all exported procedures/symbols
from a binding directory, a service program or a module:
http://www.jcrcmds.com/

I use it regularly when looking for the object holding existing
functionality and heading off potentially conflicting names.

I find binding directories are not ideal, but definitely better than the
results of my less organised mind using D*B's methods below.

-Paul.



On Fri, 24 May 2019 at 09:26, D*B <dieter.bender@xxxxxxxxxxxx> wrote:

> <Alan Shore>
> 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
> </Alan Shore>
>
> So there was meanwile a change to a binding directory. What we could learn
> by this is: changes to binding directories could affect programms running
> in
> production (greeting from pandoras box).
> As a conclusion of this, I don't use binding directories! I'm using
> crtrpgmod and CRTPGM MODULE(MOD1 MOD2 ...) BNDSRVPGM((SRVPGM1) (SRVPGM2)
> ...)
> and   CRTSRVPGM MODULE(MOD1 MOD2 ...) BNDSRVPGM((SRVPGM1) (SRVPGM2) ...)
> and
> a minimum of change management (easiest way: embedding the commands in the
> source and a little preprocessor of my own - available as freeware)
>
> <Alan Shore>
> However - does anyone know if there is a way through DB2/SQL to locate all
> the procedure names on the system?
> </Alan Shore>
>
> If you have the modules (see my recommendation above), DSPMOD
> detail(*IMPORT) and dspmod detail(*EXPORT) to an outfile and some pdm
> options are sufficient to query these files. I'm recommending to prefix
> the
> exports with the mod name, as others did and so I have enough cross
> reference information.
>
> D*B
>
> --
> 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