RE: SQL and commitment control

Were you thinking perhaps of one of these options?
https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_73/db2/rbafzskiplocked.htm

Tim Clark
DB2 for IBM i


"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> wrote on 01/01/2020
01:44:08 PM:

From: smith5646midrange@xxxxxxxxx
To: "'Midrange Systems Technical Discussion'" <midrange-
l@xxxxxxxxxxxxxxxxxx>,
Date: 01/01/2020 01:44 PM
Subject: [EXTERNAL] RE: SQL and commitment control
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxxxxxxxx>

Unfortunately, that is what I have been stumbling upon during my

research

but I was certain that there was a mode that got around that. I wonder

what

I was working on in the past...or maybe it was some weird wishful

thinking

dream that I got around it in the past.

I also found humor in the fact that your Wikipedia link discussed the

issue

related to purchase orders.

I didn't want to have to deal with temp files / members but that might

be my

only work around at this point (or a bunch of arrays to hold the data

until

the "commit"). It's not a pretty solution either way.

Thanks everyone for your help on this and Happy New Year.

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of

Bruce

Vining
Sent: Wednesday, January 1, 2020 2:31 PM
To: Midrange Systems Technical Discussion

<midrange-l@xxxxxxxxxxxxxxxxxx>

Subject: Re: SQL and commitment control

You've got a problem and one that is not unique to the i. Google 'dirty
read' and you'll find this type of exposure exists everywhere. One

write-up

is here <https://urldefense.proofpoint.com/v2/url?

u=https-3A__en.wikipedia.org_wiki_Isolation-5F-28database-5Fsystems-29&d=DwICAg&c=jf_iaSHvJObTbx-

siA1ZOg&r=oCmVbiwufH6yM8U29GriOcB5LKDoEG8y1HZD-01RVtc&m=oTb8KG3IYWxAKjmeOOIsHY3phvN3faMc1Bg3VCHfXII&s=xojcSq8sAbSxpJHkjsbkkqAbs5tNIpem1yexGPRDjFs&e=

and

removing the possibility of dirty reads essentially requires broader

locking

(delays, timeouts,...).

On Wed, Jan 1, 2020 at 2:20 PM <smith5646midrange@xxxxxxxxx> wrote:

That caused the STRSQL session to hang and eventually abend with a
record in use.

This can't be the answer because most of the other programs using the
files will not have any form of commitment control. I am only adding
it to this program so the users can cancel their changes and rollback.

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
Sam_L
Sent: Wednesday, January 1, 2020 2:15 PM
To: midrange-l@xxxxxxxxxxxxxxxxxx
Subject: Re: SQL and commitment control

It may depend on how the interactive SQL is started, Does STRSQL
COMMIT(*CS)
make any difference?

Sam

On 1/1/2020 12:31 PM,
smith5646midrange@xxxxxxxxx wrote:

I have an RPGLE program that I adding commitment control. When I
insert records to my file but have not yet committed them, I can go
to a second session and using interactive SQL, I can see them. When

I do a rollback in the program, they disappear (as I would expect).