|
If you're running it under STRDBG then maybe it says so in the joblog. STRDBG is supposed to log more about the query optimizer. Rob Berendt ================== Remember the Cole! tomh@simas.com Sent by: To: RPG400-L@MIDRANGE.COM owner-rpg400-l@MI cc: DRANGE.COM Subject: Re: Files left open after SQLRPGLE is finished 10/18/00 03:11 PM Please respond to RPG400-L 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 +---
As an Amazon Associate we earn from qualifying purchases.
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.