×
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.
<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
As an Amazon Associate we earn from qualifying purchases.
This thread ...
RE: [EXTERNAL] Re: 2 same named procedures in 2 separate service programs, (continued)
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.