RE: SQL stored procedures and activation groups via JDBC

Mark S. Waterbury wrote:

Hi, all:

An IBM i5/OS customer is running DB2/400 SQL stored procedures from a PC
via a Java-based client using JDBC ...

This runs in the QZDASOINIT job -- the top level program is QZDASOINIT,
which is itself an ILE *PGM created with ACTGRP(*CALLER) but for some
reason it runs in the default activation group (*DFTACTGRP) ... :-o

The problem is, they have commitment control, triggers, etc., and the
application programs, triggers and stored procedures etc. are all
writtin in ILE RPG IV and compiled using CRTRPGMOD and CRTPGM and set up
to run as "true" ILE programs with ACTGRP(*CALLER) as they were never
intending to run them in the *DFTACTGRP.

Does anyone know how IBM suggests to support this kind of environment,
when accessing stored procedures via JDBC? Apparently, because
QZDASOINIT is running in the *DFTACTGRP, this is causing these ILE
programs to get activated into the DAG, which is of course a "bad idea"
and there is no way to "clean up" these programs, e.g. via RCLRSC or
RCLACTGRP, and so the jobs in the connection pool just keep growing and
growing (in terms of their storage requirements).

Any suggestions, hints or tips would be appreciated.

Thanks,

Mark S. Waterbury

Could you explain more about this? This could be anywhere from an
irritant to a severe problem (as you have so far described it).

How many of these programs do you have? Do you know what the total
space, per QZDASOINIT job, is?

Are the QZDASOINIT jobs being reused over time, or are they growing in
numbers without bound?

What are the symptoms? Long term slowdown, increased paging, or simply
more and more disk consumed?

What I would predict is that you would see the storage growth for each
of these jobs take place to a certain point over time and then simply
"top off" and not grow any more.

Whether this did more than simply waste a bit of disk space would depend
on other factors.



Larry Loen
www.applicationperformancegroup.com