Re: Identifying where *modules are used

Different ways of calling a sub-program require different ways to trace all usages.

I use /COPY in source code to share common chunks of code & explanations.
Theory is when many programs need to do similar things, it can be more efficient to write some code once, and have the identical code in many programs, then if the function needs to be updated, just update it once, test in one program, then recompile all programs that use it.

But how do we find all the programs that use it?
Currently all my uses are in applicaiton "families"
* accounting - invoices
* customer - order - schedules
But that might not always be the case.

For my needs,

for my needs SO FAR

I use GO CMDREF & send output to *OUTFILE against
which I can run a query to list all programs that use a particular file,
update a particular file, call a particular program, etc. Of course this
only works when the call is explicit. There's some code that figures out
at execution time what to call & gets it via a method that defies this
approach. There's also menus that invoke a particular program, query
definitions. Different access methods require different reverse
engineering tools.

Al Macintyre

>Other than using FNDSTRPDM (PDM option 25) to search for the CALLB op
>code, is there any other method of finding which programs use a specific
>module? Is there a file somewhere in the system that acts as a
>cross-reference that can be queried to show what programs have a specific
>module bound into that program?
>
>Regards, Jerry
>
>Gerald Kern - MIS Project Leader
>Lotus Notes/Domino Administrator
>IBM Certified RPG IV Developer
>The Toledo Clinic, Inc.
>4235 Secor Road
>Toledo, OH 43623-4299
>Phone 419-479-5535
>gkern@xxxxxxxxxxxxxxxx