RE: CRTBNDRPG, ACTGRP and the H spec

["Tyler, Matt" <mattt@xxxxxxxxxxxxxx>]

Joe you will find PLENTY of discussions on this topic in the archives, but
IMHO if you want to run a program in different act groups  (i.e., *DFT or
named) use DFTACTGRP(*NO) ACT(*CALLER).  The other thing to do is always use
DFTACTGRP(*YES) and plan on not using ILE programming concepts or use a
named act group.  Both KWDs are allowed in H-SPEC, btw.

Thank you,
Matt Tyler
WinCo Foods, Inc
mattt@wincofoods.com

-----Original Message-----
From: Joe Pluta [mailto:joepluta@PlutaBrothers.com]
Sent: Friday, January 31, 2003 09:46
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

_______________________________________________
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.