Re: How to find which modules are in use in a program?

[Dave Mahadevan <mahadevan@xxxxxxxx>]

Charlie Massoglia wrote:

> Date wrote:
> >
> >It is irritating me that I cant figure out by using DSPPGM which
> modules
> >are actually used in the program.  Let me explain by an example.
> >
> >Modules:  A, B, C, D
> >
> >Program X uses A,B  (by callb or callp or procedure use).  I can do
> >CRTPGM X MODULES(A B C) .  Note C is not used by X.  If you do DSPPGM
> it
> >will tell you that C is one of the modules in the program.  If I use
> >BNDDIR to create the program, only A B will be in the program (which
> is
> >what I want, but dont want to create a binding directory for a
> program
> >nor a binding directory containing all modules since CRTPGM will
> >crawl.).  Short of specifying no modules and doing CRTPGM and then
> >looking at the Joblog on the failed CRTPGM  to find which modules are
>
> >required, is there a better method?  Service program/binding
> directory
> >idea does not appeal to me either.
> >
> > I do many modules in a program and then for some reason a module is
> >removed because it is not required anymore.   Also, this will allow
> me
> >to remove those stray modules that are no longer in use by any
> program.
> >
> >--
> Create a single binding directory.  Add all service programs (if any)
> to the
> start of the directory.  Then add all modules to the end of the
> directory.
> When you execute CRTPGM, you only have to remember the name of the
> entry
> point module if you specify the binding directory.
>
> We do not create binding directories for individual programs.  We
> create
> them for an application.
>
> Also, we always name the program the same name as the entry point
> module.
> It makes things easier to track.
>
>

I have used this approach as I mentioned earlier by putting everything
in a binding directory, but CRTPGM crawls literally.   And locks all the
modules in the binding directory to boot when it is crawling.  I am sure
there is a better solution.

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the Midrange System Mailing List!  To submit a new message,   *
* send your mail to "MIDRANGE-L@midrange.com".  To unsubscribe from     *
* this list send email to MAJORDOMO@midrange.com and specify            *
* 'unsubscribe MIDRANGE-L' in the body of your message.  Questions      *
* should be directed to the list owner / operator: david@midrange.com   *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *