Explicitly closing SQL cursors

[Frank.Kolmann@xxxxxxxxxx]

Hi Matt,
I absolutely agree, but SQL likes to leave ODPs open even if
one does an SQL CLOSE.  The programs that give me most
grief dont even use SQL cursors. It is most likely an SQL
performance issue to leave cursors open.
What got me is that the ILE SQL compile option is the
opposite to OPM in that OPM closes cursors at *ENDPGM.

Frank

Matt Wrote:
>Frank,
>
>You should be explicitly closing your cursors when you are done with them.
>It is bad programming practice to leave them open and let the system
>automatically close them.
>
>Matt
>
>Subject: RE: Cvt RPG III to RPG IV (strange problems )
>Date: Mon, 19 Aug 2002 10:03:00 -0400
>From: "Haas, Matt" <Matt.Haas@thomsonlearning.com>
>
><snip>
>I have to be really careful with SQL programs CRTSQLRPGI.
>CLOSQLCSR( *ENDACTGRP)  is the default whereas with
>CRTSQLRPG  CLOSQLCSR( *ENDPGM ). Cursors are staying open
>when I expect them to be closed. Perhaps I should change the
>(*ENDACTGRP) to (*ENDMOD) permanently.
>When the SQL cursors remain open and the file was locked
>with ALCOBJ occasionally the lock REMAINS even when the user
> has exited the program completely.
><snip>