RE: SQL Locking...

But we're not locking on the record we are attempting to update. We are
locking on the record we are attempting to get data from.  

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Alan Shore
Sent: Friday, November 17, 2006 12:49 PM
To: Midrange Systems Technical Discussion
Subject: Re: SQL Locking...

Dave - wont the same thing happen if you attempt to update a record in
RPG/RPGILE/COBOL etc, if the program does NOT have a lock on that
record.
If another user has a lock on that record, the program cannot get an
exclusive lock



Alan Shore

NBTY, Inc
(631) 244-2000 ext. 5019
AShore@xxxxxxxx

midrange-l-bounces@xxxxxxxxxxxx wrote on 11/17/2006 01:39:01 PM:

I have a fellow programmer who has this code in a CL program:

Update OEP013W a set a.wkclosr =
   (select mtclon from OETITLP b where a.wkorder = b.mtordn)
   where a.wkclosr = 0

Where OEP013W is a work file in QTEMP; OETITLP is a production PF.

If someone is in the record (locking it) this statement fails.

If you do the sub-SELECT statement by itself with someone locking the 
record, it doesn't fail.

Does a SELECT in an UPDATE statement have different rules?

It was our understanding that a SELECT did not lock, or require a 
lock, and we assumed would not be inhibited by someone else locking a 
record in that file.

TIA

Dave

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, 
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take 
a moment to review the archives at 
http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.