Re: Suggestion: File to use when compile

Hi,

> One limitation of that, is that it doesn't also support any pre/post
> commands to prepare the compile environment, such as overrides or
> special library list requirements, etc.  I like being able to simply
> put a PDM option in front of any member (or set of members via
> FNDSTRPDM) and know it will correctly establish the environment and
> recompile the member(s).

Actually, what it does is run DSPPGMREF to an *OUTFILE, see where each
file that you referenced last time you built the program was, and do an
explicit override for each file before compiling it again.

So, you have to type the overrides the first time you compile it, but in
subsequent compiles, it looks up what you did last time and does it for
you.

However, I don't use the various "work with" panels in PDM.  I do
everything from the command line.  I do use FNDSTRPDM to search for
strings, though.


> It also lets me move source from a development machine to production
> and compile without having to set/change the parms I want on that
> machine once first.

That's very true. You have to do a fresh compile when you move the
program into production.

The nice thing is, you can use it for programs that were compiled 10 years
ago before we had the utility, and it works just as well.  So, it's very
useful for mass recompiles of programs when a field has been added to a
file, etc.

I've often thought about writing a utility like yours. Or simply having
one CL program to compile each RPG program.  Or using a MAKE utility, like
I do in Unix...