Fw: Embedded SQL & commitment control

Sorry, check that... RR is Serializable in SQL, RR on command...


-----Original Message-----
From: R. Bruce Hoffman, Jr. <rbruceh@attglobal.net>
To: RPG400-L@midrange.com <RPG400-L@midrange.com>
Date: Wednesday, March 14, 2001 8:52 AM
Subject: Re: Embedded SQL & commitment control


>-----Original Message-----
>From: Phil Groschwitz <sublime78ska@yahoo.com>
>To: RPG400-L@midrange.com <RPG400-L@midrange.com>
>Date: Wednesday, March 14, 2001 12:37 AM
>Subject: Embedded SQL & commitment control
>
>
>>
>>The file gets locked *SHRRD, which means the select
>>statement can still occur after another job's select
>>and before that job's insert.
>>
>>Could someone please show where I've gone astray?
>
>I am not sure what you are asking. You may have to elaborate.
>
>But reads on SQL are not held locked unless it is for update.
>
>Reads without update are not normally held by RPG.
>
>If you are trying to lock the file exclusive... the commit level is
>REPEATABLE READ.
>===========================================================
>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
+---