RE: RCLACTGRP Issue

Hi Eric -

I'll grant that *caller service programs CAN work, but from the perspective
of an ILE newbie, (imo) it's probably not a good idea.  It really depends on
how the service program was written.  In this case, with an application
designed to use RCLRSC to "shut down" program resources left open, then
ported into ILE, it seems particularly chancy to activate these service
programs into the DAG.

Our application software has no RCLACTGRPs.  I don't think it has any
RCLRSCs either.  It certainly doesn't where any service programs are in use.

As far as releasing resources, I write all of my service programs with a
procedure to close the resources, and most have a procedure to open them as
well.  At least one, maybe two, open resources only as needed because of
the nature of the services they provide.

I have an advantage over a lot of people in that there was no use of ILE
functions where I work before I started it.  All RPG IV programs used to be
compiled with DFTACTGRP(*YES).  I write and maintain all of our service
programs so I make sure that they adhere to the ILE standards that I
developed, said standards including:
1. all service programs are *CALLER.
2. no named activation groups for service programs or regular programs.
(Someone could compile a regular program into a named activation group, but
since I provide a set of standard H-spec /COPY members with activation
group keywords, it's very unlikely.)

Ken
Opinions expressed are my own and do not necessarily represent the views of
my employer or anyone in their right mind.