Re: _iqlocate_cursor Arguments(esql)

Judging from the source code, the second argument is the cursor type. Exactly what the coding means I have deliberately not investigated, but at a guess you've changed the cursor from an ordinary one into a scroll cursor, or added the WITH HOLD attribute, or some such change. Consequently, I think that you do not have a bug in the generated code. There may be a bug in the underlying library, but not in the code. You should not change the calling sequence. Are you freeing your cursors (and prepared statements) correctly? Are you aware that the rules changed between versions 4 and 5? If not, please go and double-check what it says in the manual, and in the release notes. Yours, Jonathan Leffler (johnl@informix.com) #include <disclaimer.h> }From: msm@spaceworks.com (Michael Mstowski) }Subject: _iqlocate_cursor Arguments(esql) }Date: Mon, 14 Nov 1994 18:21:16 GMT }X-Informix-List-Id: <news.9788> } }I'm running informix esql 5.02 and Online 5.03 on HP/UX. The esql engine }generates the wrong arguments for a function call names _iqlocate_cursor. }For example: }_iqlocate_cursor(_CN2,0,0) }should be }_iqlocate_cursor(_CN2,2,0) } }The first example above causes a huge memory leak in the sqlturbo process. }The second one makes the memory leak go away. Both examples work. The }fix was found by trial and error. The question is what really is the }second argument to _iqlocate_cursor and what does it mean??? } }Thanks in advance. }Michael Mstowski }msm@spaceworks.com