× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: Files left open after SQLRPGLE is finished
  • From: tomh@xxxxxxxxx
  • Date: Wed, 18 Oct 2000 15:11:03 -0500


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



As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.