RE: embedded SQL loop leaves multiple files open

I have an SQLRPGLE program that has the loop that does 300 different SQL execute immediate statements each of which performs a join on the same 4 tables .
I've yet to determine why, after the program completes, DSPJOB OPTION(*OPNF) shows 300 open file entries for each of the 4 files (1200 open file entries)
I figure this is not really a good thing.

The program uses *CALLER but the top level program was developed as an OPM CLP which means that everything run in *DFTACTGRP (which I hate to see)

Peter


-----Original Message-----
From: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of D*B
Sent: Saturday, 5 July 2014 5:22 p.m.
To: RPG programming on the IBM i / System i
Subject: Re: embedded SQL loop leaves multiple files open

... normally those open data pathes don't hurt if the database keeps them open for performance reasons. CLOSQLCSR does lazy closes as the SQL close operations too (BTW: best practice is to issue a close when no longer needed and CLOSQLCSR should have no work to do, neither at endmod, nor at endactgrp). A disconnect should close them hard, this would implicit happen, if you specify ACTGRP(*NEW).

D*B