RE: Eliminating *MODULES with IMPORT and EXPORT parms and replacingthem with Service Programs

We use this in our header copybook. RDi (we don't have RDp - and
probably won't for a while) doesn't like this for verifies, but it
compiles just fine.

H bnddir('UMEDBNDDIR':'QC2LE')
H copyright('Copyright 2009 MEDTRON Software Intelligence')
H debug(*yes) option(*srcstmt:*nodebugio:*showcpy:*expdds)
/if defined(#CALLER)
H dftactgrp(*no)
H actgrp(*CALLER)
/elseif defined(#new)
H dftactgrp(*no)
H actgrp(*new)
/elseif defined(#service)
H Nomain
/elseif defined(#sql)
/else
H dftactgrp(*no)
H actgrp('QILE')

When we create our service programs, we set the ACTGRP as part of the
compile. Our CMS has it loaded for each service program, so no need to
remember on each of them.

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of
GKern@xxxxxxxxxxxxxxxx
Sent: Wednesday, April 13, 2011 12:42 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: RE: Eliminating *MODULES with IMPORT and EXPORT parms and
replacingthem with Service Programs

<snip>

We have an H spec copybook with the following:

H Option(*NODEBUGIO : *SRCSTMT)
H BNDDIR('MASTER') BNDDIR('QC2LE')
H DFTACTGRP(*NO)
H ACTGRP(*CALLER)

The one area that I have concerns with here is the ACTGRP(*CALLER) entry

in the H spec copybook. My concern lies in that we may have some OPM
programs that would result in running the the default AG. My thought is
when compiling service programs we should use the service program name
for
the activation group parameter on the CRTSRVPGM. (That was a suggestion
from another thread awhile back here on RPG-L).

<snip>




Kevin Bucknum
Senior Programmer Analyst
MEDDATA/MEDTRON
Tel: 985-893-2550