Re: Activation groups documenting -- RPG400-L

Hi Bob -

We have used two basic activation groups, *DFTACTGRP and QILE.

The problem is that the rules for each group have not always been clear or even followed to the letter. Now I would like to clean up the activation groups and create a listing of pgm objects with activation groups to assist programmers when recompiling programs in the future.

I'll second Bob Cozzi's suggestion to use H-specs to specify the activation groups. That makes recompiling the programs a no-brainer.

I do it by way of /copy members. I have three members: hnew, hcaller, and hsrvpgm.

hnew specifies DFTACTGRP(*NO) ACTGRP(*NEW)
hcaller specifies DFTACTGRP(*NO) ACTGRP(*CALLER)
hsrvpgm specifies NOMAIN

All of these also contain OPTION(*SRCSTMT *NODEBUGIO) and
BNDDIR([the binding directories we use])

We use hnew and hcaller for regular RPG IV programs. We do not use named activation groups. Programs that run in the default activation group do so by virture of being ACTGRP(*CALLER) and called from within the default activation group (or a programmer didn't use one of the /copy members). Our regular RPG IV programs always consist of just one module. Sometimes they have internal procedures. If they have external procedures that I have written, those are always in service programs, never in modules bound by copy.

I use hsrvpgm for modules that are to be bound into service programs. Most of my service programs consist of one RPGLE module. In a couple of cases I also have a CLLE module bound in. I create all of my service programs as ACTGRP(*CALLER). (I do all of our service program creation and maintenance.)

I know that there are a lot of people on this list who disagree with the way that I use activation groups (so don't bother to reply telling me that I'm doing it wrong). On the other hand there are people who agree with my way. I started the use of true ILE functions here and set the standards. They work great for me and the other programmers here.

-- Ken http://www.ke9nr.net/ Opinions expressed are my own and do not necessarily represent the views of my employer or anyone in their right mind.

This mailing list archive is Copyright 1997-2024 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.