RE: Activation Group Issues ?

This technique is a novel idea and a lot of people talk about it because it
seems to be an easy concept to grasp. But so is pointing a gun at a mosquito
and pulling the trigger. Some people realize that it is overkill before they
get too far into it.
Things like embedded SQL are a far better solution if you need this
capability. Writing setters and getters for accessing database information
(in RPG IV) is a youthful indiscretion that you be well advised to avoid.

If your application was calling a setter or getter for a single I/O process
whereby you were, for example, retrieving application settings once during
an application invocation, then that's a great idea. But replacing native
database I/O with setters in getters reminds me of line from Crocodile
Dundee. (and I am paraphrasing) "You can do it, but it works like $hit."

-Bob Cozzi
www.RPGxTools.com
RPG xTools - Enjoy programming again.


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Fleming, Greg (ED)
Sent: Tuesday, November 08, 2005 3:48 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: Activation Group Issues ?

We're still relatively wet behind the ears with ILE here, but we're
moving forward with what we've been able to learn, and I think I may
have run into an activation group issue.

 

I have an RPG program which uses a procedure in a service program to
populate fields in the output file based on a key passed to the
procedure.

 

I may use the same procedure several times in a row to populate
different flags based on various keys, like so:

 

CallFlag  = S_MKIUFD_getVerticalFlag(K#Comp:HLJYNB:HLFQNQ:'CAL');

EmailFlag = S_MKIUFD_getVerticalFlag(K#Comp:HLJYNB:HLFQNQ:'EML');

FaxFlag = S_MKIUFD_getVerticalFlag(K#Comp:HLJYNB:HLFQNQ:'FAX');

HTMLFlag = S_MKIUFD_getVerticalFlag(K#Comp:HLJYNB:HLFQNQ:'HTM');

MailFlag = S_MKIUFD_getVerticalFlag(K#Comp:HLJYNB:HLFQNQ:'MAI');

RentFlag = S_MKIUFD_getVerticalFlag(K#Comp:HLJYNB:HLFQNQ:'REN');

 

 

The program seems to be running significantly longer than it used to
before I added this code.  

 

My service program has the Activation group set to *Caller, and "Shared
Activation Group" = *No.

 

I've done some reading on Activation groups in the ILE Reference, but
it's made my head go wobbly.  I'm guessing maybe I should update my
service program and change the shared activation group attribute to
*Yes.  

 

Or am I totally barking up the wrong tree, and maybe I should scrap the
service programs altogether and bind the procedures at compile time ? 

 

Any thoughts or helpful suggestions would be greatly appreciated.  

Greg Fleming

Programmer/Analyst

Everglades Direct, Inc.