Antw: RPG Stored Procedures, SQL, and Closing files/ActivationGroups

Dwight,

we have the same problem, but we have been creating SQL stored procedure
with SPL (stored procedure language).
- we are using SQL fetch in the stored procedure:

   Open C1;
   Fetch C1 into VAR1;
   While End = 0 Do
       ...
       Fetch C1 into VAR1;
   End If;
   End While;
   Close C1;

- with SPL we have only global defined variables
- we are not returning a result set so we can close the cursor prior to the 
return
- the stored procedure is not called from Visual Basic etc.
- the stored procedure is called from another SQLRPGLE in QBATCH
- the SQLRPGLE is compiled with CLOSQLCSR(*ENDACTGRP)

Our Batchjob is logging many messages (> 6000 pages of joblog)  that
the cursor is not open during a fetch or close.

Now you can reduce the reasons for our problem.

Alexander



>>> dslessman@nationalelectrical.com 06.11.02 18:21 >>>
Hello all,

We have been creating ILE RPG stored procedures to fetch, edit, and update
information contained in our databases.  The stored procedures are called
from both Visual Basic and Apache/Tomcat (running on Windows and being
called through the JDBC driver and pooling).  The stored procedures are all
compiled with CLOSQLCSR(*ENDACTGRP) we were hoping for performance reasons.

The stored procedures use embedded SQL to perform the database I/O.
Everything is working quite well and our users are pleased with what we
have been able to do.

My question is this:  In the "fetch" stored procedures we use a SQL prepare
(from an RPG variable that we build on the fly), SQL declare, SQL open,
then SQL set result sets cursor. The stored procedures than issue a
"RETURN" with "LR" off.

On the first call to the stored procedure life is good and the expected
results are returned.  On subsequent calls life was not as good (cursor was
already open).  We started putting in a close to the cursor (whether it was
open or not).  The server jobs of course are now logging many messages that
the cursor is not open during a fetch or close.

I have since attempted to place logic in the stored procedures to only
issue the close if the file is open but subsequent calls to the stored
procedures do not seem to be maintaining my variable information.

I am sure someone out there has already resolved this.  The applications
are running fine I am just trying to reduce some of the messages that are
logged in the server's job logs.

Any ideas?

Thanks,

Dwight Slessman

_______________________________________________
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l
or email: RPG400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.