|
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.
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Barbara Morris
Sent: Tuesday, October 12, 2004 7:12 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: Re: Suggestion: File to use when compile
Lim Hock-Chai wrote:
>
> 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
>
What you specify on the H spec already overrides the parm values.
/IF DEFINED(*CRTBNDRPG)
H BNDDIR(STDBNDDIR)
/ENDIF
(By the way, BNDDIR is valid for CRTRPGMOD too.)
--
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.