Re: CLOSQLCSR=*ENDMOD

I assume that the linker knows where the code boundaries are in the program - so a module has some existential validity within a program. There is probably some discussion of this in the ILE Concepts manual or the ILE Example manual.

So although there is not a separately-executable object called a *MODULE, the *MODULE does contain executable code that is linked. The system has to know where any executable code comes from.

On 11/1/2011 8:55 AM, Gary Thompson wrote:

Hockchai Lim wrote:

CLOSQLCSR=*ENDMOD ==> SQL cursors are closed and SQL prepared statements
are implicitly discarded when the module is exited. LOCK TABLE locks are
released when the first SQL program on the call stack ends.

can someone help me understand what “when the module is exited” in the
above statement means? As far as I know, module object is not an
executable object. So, I couldn’t quite understand what it mean?

I can't answer your question about module closing, but I find
*ENDMOD useful when debugging. When specified, I can
repeatedly call the program being debugged and the cursor
"works as expected" - meaning, on subsequent calls, the
cursor starts with the first row.