Re: Embedded SQL & commitment control

["R. Bruce Hoffman, Jr." <rbruceh@xxxxxxxxxxxxx>]

-----Original Message-----
From: Phil Groschwitz <sublime78ska@yahoo.com>
To: RPG400-L@midrange.com <RPG400-L@midrange.com>
Date: Wednesday, March 14, 2001 1:09 PM
Subject: Re: Embedded SQL & commitment control


>Problem is that the record doesn't get locked when I
>do the select.  Somewhere in the documentation I read
>that inorder for the lock to span more than just the
>select statement, I had to use a cursor so that's why
>I'm using the cursor rather than just a select and an
>insert - so that I can define a transaction.
>
>I don't want to lock the entire table - just the row
>so I won't get any duplicate keys.
>


Yeah, see the row must be selected for Update when not using the
serializable on set transaction.

On the cursor you might try adding the "for update" clause to the select in
the cursor declaration.


===========================================================
R. Bruce Hoffman, Jr.
 -- IBM Certified Specialist - AS/400 Administrator
 -- IBM Certified Specialist - RPG IV Developer

"America is the land that fought for freedom and then
  began passing laws to get rid of it."

     - Alfred E. Neuman



+---
| 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
+---