Re: Files left open after SQLRPGLE is finished

Tom,

You might look at the activation group for the open files.  This is most likely 
not the 
problem, but a *CALLER trigger that is fired from an embedded SQL statement 
will 
run in the default activation group.  Any files opened by the trigger will be 
opened 
in the default activation group and will not close.

David Morris

>>> tomh@simas.com 10/18/00 02:11PM >>>
Thanks to all who replied.  I am indeed using cursors, and am 99% sure 
that I'm closing all of them as I 'return' from each subprocedure that 
creates/uses them. Compiling with *ENDMOD did the trick, but I'm still 
curious as to why some of the files were being left open, even though I 
verified with STRDBG that I'm doing the close cursor command.

For example: a file called EDI001L5.  Though I don't reference this file 
(directly) in my program, it's being opened and left open.  I have a SQL 
'select * from EDI001PF where ....'; I suspect the system is using the L5 
because it's the 'best' access path for the file at that time.  The SQL 
'close cursor' is missing it because the 'open cursor' is for the 
EDI001PF, not EDI001L5. Am I on the right track?






>I've written an SQLRPGLE program which, from time to time, is leaving the
files open that the SQL statements process - >even after *INLR is on and
the program ends.  How can I force all files opened by the program to 
close
at *INLR?


What did you use for the following create parameter?

Create SQL ILE RPG Object (CRTSQLRPGI)

 Close SQL cursor . . . . . . . .   *ENDMOD      ( *ENDMOD, *ENDACTGRP )


John Carr



+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---