RE: SQL Locking...

Dave,

I wonder if commitment control is causing a problem...

Try:

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



Charles Wilt
--
iSeries Systems Administrator / Developer
Mitsubishi Electric Automotive America
ph: 513-573-4343
fax: 513-398-1121
  

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx 
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Turnidge, Dave
Sent: Friday, November 17, 2006 1:39 PM
To: Midrange Systems Technical Discussion
Subject: SQL Locking...

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.