RE: Advice with Activation Groups and Stored Procedure Programmes

[Alan Campin <Alan.Campin@xxxxxxx>]

The one thing you should be noticing is a big reduction in performance. Running 
an External Stored Procedure, i.e. a program in a *NEW means that every time 
you call it recreates the activation group. Talk about destroying performance. 
Great way to do it. Have you tried just using a named activation group like 
QILE or something?

The other thing that using *NEW tells me is you have some kind of programming 
bug that you are fixing by recreating the activation group each time. Just like 
wiping the slate clear each time. You have some variable that is retaining a 
value between calls where *NEW wipes it clean. Fixes the problem but what a 
cost.  

Other stuff I am not clear about. Just watch the SQL run and see what 
activation group the various pieces are running using option 14 on a DSPJOB. I 
know that if you are writing triggers, the manuals say always have the trigger 
program run in *CALLER. 

I have written a lot of external stored procedures but in RPG/ILE and always 
just ran in named activation group QILE and never had any issues. 

-----Original Message-----
From: PAPWORTH Paul [mailto:Paul.Papworth@xxxxxxx]
Sent: Monday, May 02, 2005 2:47 AM
To: rpg400-l@xxxxxxxxxxxx
Subject: Advice with Activation Groups and Stored Procedure Programmes


We have  server programmes (Java)  that use JDBC which in turn runs the
QZDASOINIT job in order the access data in our I Series.  External
Stored Procedure (RPG COBOL ...) programs are a means used to access the
data base. We have recently had problems  which we have overcome by
changing the activation group of certain external stored procedures form
*CALLER to *NEW, but we would like to understand why this overcame the
problem.=20

I have 3 questions

Does anybody have any advice as to how we should be defining our
activation groups with external stored procedure programmes ?

Does the QZDASOINIT job open all external stored procedures in the
default activation group ?

External stored procedure programs are usually written using SQL
(Result Set) Are there any caveats as regards activation groups and
stored procedures. We have the impression that SQL executes in an
activation group apart from the host external stored procedure program.
?

=20

Many thanks for any help that you can give.

=20

Paul Papworth      =20