RE: Suggestion: File to use when compile

["Dan Bale" <dbale@xxxxxxxxxxxxx>]

Ya, that is how mine came to be.  When I have enough of "why should I have
to do this" moments, I try to build a better mousetrap.

Would it be nice if IBM would build in this function?  You bet.  For it to
be truly useful, though, when prompting PDM option 14 on a member that has
parameter overrides embedded, those overrides should show up on the prompted
command.  Given that some change commands show current values when prompted
(prompt CHGJOB, press F10 for example), it shouldn't be that hard to do.
(Wheels are turning again!)

db

> -----Original Message-----
> From: rpg400-l-bounces@xxxxxxxxxxxx / Lim Hock-Chai
> Sent: Wednesday, October 13, 2004 9:37 AM
>
> yes, for that particular parm.  The suggestion is really more
> focus on a flexible compiler directive that can override any parm
> in the create command without us have to wait for new keyword.
>
> for example:
> If I'm compiling a PF using CRTPF.  I would want to be able to
> have the following in my DDS
>       /OVRPARM MAXMBRS(5) SIZE(*NOMAX)
>
> If I'm compiling a PRTF usign CRTPRTF.  I would want to be able
> to have the following in my DDS
>       /OVRPARM PAGESIZE(68 80)
>
> If IBM add a new parm to CRTBNDRPG command.  I would want to be
> able to have the following in RPG source
>       /OVRPARM NEWPARM(VALUE)
>
> The main objective would be a compiler directive that is
> flexiable enough that developer would not need to wait for new
> keyword to be added.