RE: Suggestion: File to use when compile

["Lim Hock-Chai" <Lim.Hock-Chai@xxxxxxxx>]

Although I'm concerned about it, I'm all for it if ibm provides /precmd and 
/postcmd.

As for override parameter, not sure I understand what you mean.  The objective 
is to not have to remember to prompt and change it each time developer 
compile/recompile a program.

Yes, you could do /postcmd chgprtf cpi(15) to get around it.  However, some 
parms can not be changed after object has been created and some have to be 
specified when compiling program  

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Denis Robitaille
Sent: Wednesday, October 13, 2004 3:58 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: RE: Suggestion: File to use when compile


My 2 cents:

We have been using this kind of stuff (compiling instructions in the
source read by a utility program) for close to 10 years. It is used on a
daily basis by over 60 programmers (some hold, some new, some
contractor, some student ...). The advantages far outweigh the problem.
Now nobody forget to specify CPI(15) on a printer file or an override
before a compile anymore.

As for overiding some parameter when compiling, our utility allows it.
Instead of pressing enter, we press F4 and answer YES to a show command
prompt and we can then change it for this time only without having to
change the source. 

In fact, we dont use option 14 of PDM anymore (we now use the home made
CP instead)