|
I've written my own utilities to do this. For me, the hard part isn't figuring out what modules make up a program, the hard part is figuring out all the other compilation options, such as actgrp(), file overrides, etc. For finding the mocules, I have a program which ends with LR off. The first time that its called, it dumps all the programs/modules on the system into QTEMP using the QBNLPGMI API. Then, each subsequent call, it searches that user space to find which programs use a given module. Then I have another utility called "RECRT" (recreate) which takes a given program name and finds out how it was compiled the last time. It finds out things like ACTGRP(), DBGVIEW(), file names & where they were overridden to, etc. Then it recompiles each module and binds it into a program. The system works pretty well, but the programming to create it was a bit complex... HTH On Tue, 26 Dec 2000, Jade Richtsmeier wrote: > We all know that when a file changes, all the programs that use that > file need to be recompiled. When using ILE, how do you do a mass > rebuild of all the objects that use the file? > > Do you use CL to keep track of what modules/service programs and such > make up a program? Are there utilities available that help with this > sort of thing? Or, does it just become a manual process? > > We're looking for ideas as how this is all managed, and would > appreciate any input. > > Thanks! > Jade > +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
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.