Re: actgrp for service program

["Keith Carpenter" <CarpCon@xxxxxxx>]

Here's why I asked...

If you think about it, specifying a BNDDIR on a module is really a directive
(reference) for PGM/SRVPGM creation.   It's not needed for module creation.

With the V5R3, CRTPGM's default for ACTGRP was changed from *NEW to *ENTMOD
(entry module).  *ENTMOD determines whether to use QILE, QILETS or *NEW
based on the main (entry) module's language type (ie. RPG, Cobol, C)

It would seem that _IF_ an ACTGRP could be specified at module creation,
then a CRTPGM ACTGRP(*ENTMOD) _COULD_ use this value rather than the new
defaults (QILE or *NEW).

Just a suggestion.


Keith


----- Original Message ----- 
From: <CWilt@xxxxxxxxxxxx>
To: <rpg400-l@xxxxxxxxxxxx>
Sent: Tuesday, August 03, 2004 1:14 PM
Subject: RE: actgrp for service program


> Nope,
>
> Think there's some confusion going on.
>
> You and the OP are talking modules (option 15)
>
> ACTGRP and DFTACTGRP don't apply to a module.  They are specified when you
> do the CRTPGM not the CRTRPGMOD.
>
> Look at the other's examples, you'll see that ACTGRP and DFTACTGRP are
only
> used when CRTBNDRPG is being used:
>
>
> HTH,
> Charles
>
>
>
>
> > -----Original Message-----
> > From: Keith Carpenter [mailto:CarpCon@xxxxxxx]
> > Sent: Tuesday, August 03, 2004 4:00 PM
> > To: RPG programming on the AS400 / iSeries
> > Subject: Re: actgrp for service program
> >
> >
> >
> > Is this a V5R3 change ?
> >
> > On V5R2,  I get an error when I try to specify
> > H NOMAIN ACTGRP('MYAG')
> > for a module (PDM 15 or CRTRPGMOD).
> >
> > Same error as prior releases...
> > *RNF1324 20      1 Keywords DFTACTGRP, ACTGRP, or USRPRF are
> > not allowed
> >
> >
> > Keith
> >
> >
> >
> > ----- Original Message ----- 
> > From: "Bob Cozzi" <cozzi@xxxxxxxxx>
> > To: "'RPG programming on the AS400 / iSeries'" <rpg400-l@xxxxxxxxxxxx>
> > Sent: Tuesday, August 03, 2004 12:30 PM
> > Subject: RE: actgrp for service program
> >
> >
> > > When compiling a NOMAIN module using PDF option 15 or the CRTRPGMOD
> > command,
> > > the DFTACTGRP(*NO) keyword may NOT be specified on the
> > HEADER spec in the
> > > source.
> > > If you're using PDM option 15 or the CRTBNDRPG command,
> > then both the
> > > DFTACTGRP(*NO) keyword and the ACTGRP('MYAG') keyword may
> > be specified.
> > > However, if you do not specify DFTACTGRP(*NO) and you (for
> > some reason)
> > try
> > > to compile with PDM option 14, you will get the error
> > you've reported.
> > > I usually code the following on my Header specs just for
> > good measure:
> > >
> > > .....H  OPTION(*NODEBUGIO : *SRCSTMT)
> > >      H/IF DEFINED(*CRTRPGMOD)
> > >      H  NOMAIN ACTGRP('MYAG')
> > >      H/ELSE
> > >      H  DFTACTGRP(*NO)  ACTGRP('MYAG')
> > >      H/ENDIF
> > >
> > > -Bob Cozzi
> > >
> > >
> > > -----Original Message-----
> > > From: rpg400-l-bounces@xxxxxxxxxxxx
> > [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
> > > On Behalf Of michaelr_41@xxxxxxxxxxxxxx
> > > Sent: Tuesday, August 03, 2004 2:15 PM
> > > To: RPG programming on the AS400 / iSeries
> > > Subject: Re: actgrp for service program
> > >
> > > That's the way to do it. You also have to specify
> > DFTACTGRP(*NO) in the
> > > Header spec.
> > >
> > > On Tue, 3 Aug 2004 13:35:05 -0500, "Lim Hock-Chai"
> > > <Lim.Hock-Chai@xxxxxxxx> said:
> > > > Is there a way to hardcode the activation group in the
> > RPG source?  I
> > > > tried to use ACTGRP keyword in the H spec but getting the
> > compile error
> > > > when try to create the module.
> > > >
> > > > thanks.
> > > >
> > > >
> > > > --
> > > > 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.
> > > >
> > > -- 
> > >
> > >   michaelr_41@xxxxxxxxxxxxxx
> > >
> > > --
> > > 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.
> > >
> > >
> > >
> > > --
> > > 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.
> > >
> >
> > --
> > 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.
> >
> --
> 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.
>