RE: Suggestion: File to use when compile

I like the idea of using keyword.  Compiler executing any command in the 
program source sound a bit scary for me.  However, it would be nice if ibm can 
also add a compiler directive (/OVRPARM) to override parm values.  For example:

      /IF DEFINED(*CRTBNDRPG)
      /OVRPARM BNDDIR(STDBNDDIR)
      /ENDIF





-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Joe Lee
Sent: Monday, October 11, 2004 5:27 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: RE: Suggestion: File to use when compile


So for example in
the code below, assuming the new keyword is COMPILENAME, when the
compiler ran instead of looking for file CUSMASTDDM, it would look for
file CUSMAST and use it's properties. This would also be very useful for
the new EXTFILE and EXTMBR keywords.

FCUSMAST   IF   E           K DISK  
FCUSMASTDDMIF   E           K DISK    usropn COMPILENAME('CUSMAST')

Joe Lee

>>> rob@xxxxxxxxx 10/11/2004 14:38:32 >>>
But precompile commands, on separate objects might be a bit trickier.
Like 
a CRTPF QTEMP/MYFILE... OVRDBF MYFILE QTEMP/MYFILE...
At least, that should be a separate DCR.

You might be tilting at windmills to try to get IBM to add this in to
the 
commands but it sure can't hurt to try.