RE: CRTBNDRPG, ACTGRP and the H spec

[Scott Mildenberger <Smildenber@xxxxxxxxxxxx>]

Joe,

     h dftactgrp(*no)

Also, there are now keywords *CRTBNDRPG and *CRTRPGMOD that you can use with
conditional compilation (/if defined) to have different h spec keywords
depending which compile command is being used.

Scott Mildenberger

> -----Original Message-----
> From: Joe Pluta [mailto:joepluta@PlutaBrothers.com]
> Sent: Friday, January 31, 2003 9:46 AM
> To: RPG programming on the AS400 / iSeries
> Subject: CRTBNDRPG, ACTGRP and the H spec
> 
> 
> Okay, now that I've upgraded to V5R1, I got rid of some of my 
> old standby
> commands in my user system library.  This included my special 
> version of
> CRTBNDRPG, which had DFTACTGRP(*NO) specified.
> 
> Now, I figured I could avoid this by simply specifying an 
> ACTGRP(xxx) in my
> H spec, but the compiler bombs.  Evidently the ACTGRP(xxx) 
> keyword isn't
> enough to override the CRTBNDRPG's default setting of DFTACTGRP(*YES).
> 
> This stinks.
> 
> So, do I have to know ahead of time whether a program is 
> meant to be in the
> activation group, and execute a different compile command 
> (setting DFTACTGRP
> to either *YES or *NO) depending on how the program is meant to run?
> 
> This seems to be a pain in the butt.  If I go to the trouble 
> of specifying
> the keyword in the H spec, you'd think that would override 
> any defaults the
> compiler might have.
> 
> Anyway, bottom line: do I have to go re-add my CRTBNDRPG 
> command in PBDUTIL
> to have DFTACTGRP(*NO)?
> 
> Joe
>