Re: Embedded SQL + Closing an ODP

["Bill.Freiberg" <bill.freiberg@xxxxxxxxxxxx>]

Browsing the v4r3 copy of the DB2 for AS/400 SQL Programming Guide (qb3aq802),
section 22.10 does a pretty thorough job of describing ODP handling in SQL and
options for helping to control them. Turns out that ODP state <> cursor
state...go figure.

David Keck wrote:

> I have an ILE RPG program comprised in part of an SQLRPGLE module, compiled
> with
>
> Commitment control  . . . . . . . . . . . . . . . . . :   *NONE
> Relational database . . . . . . . . . . . . . . . . . :   *LOCAL
> Naming convention . . . . . . . . . . . . . . . . . . :   *SYS
> Allow copy of data  . . . . . . . . . . . . . . . . . :   *OPTIMIZE
> Allow blocking  . . . . . . . . . . . . . . . . . . . :   *ALLREAD
> Delay PREPARE . . . . . . . . . . . . . . . . . . . . :   *NO
> Close SQL cursor  . . . . . . . . . . . . . . . . . . :   *ENDMOD
>
> After ...
>
> C/EXEC SQL open @Cursor
> C/END-EXEC
>
> an ODP is created as can be seen via WRKJOB 14.  Later, immediately after
> ....
>
> C/EXEC SQL close @Cursor
> C/END-EXEC
>
> the file is still open, which I find perplexing and vexing.  With the file
> open the program maintains a member lock which interferes with other
> elements of the system.
> How can I close the ODP and release related locks without ending the program
> containing the embedded SQL ?  A solution which works at V3R2 would be
> ideal.
>
> Thanks - Dave K.
>
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator: david@midrange.com
> +---

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---