RE: Modernization and multi-member files

So?

If you look at the DB2 SQL manual for LUW and i, you'll see the following in both:

Can the application see uncommitted changes made by other application processes?
NC - YES (DB2 for i only)
UR - Yes
CS - No
RS - No
RR - No

Can "updated" rows be read by other application processes that are running at an isolation level other
than UR and NC?
NC - Yes (DB2 for i only)
UR - No
CS - No
RS - No
RR - No

Now if you want to say that to many i jobs run at NC or UR, then I'd agree to that.


Charles Wilt
--
Software Engineer
CINTAS Corporation - IT 92B
513.701.1307
wiltc@xxxxxxxxxx

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
bounces@xxxxxxxxxxxx] On Behalf Of Terrence Enger
Sent: Thursday, July 17, 2008 10:32 AM
To: Midrange Systems Technical Discussion
Subject: Re: Modernization and multi-member files

Greetings,

I am almost scared to contribute again to a thread which has generated
so much heat. No doubt I shall be sorry. Still, here goes ...

Much of the intervening discussion seems to me to be talking about
issues which are, viewed from 50,000 feet, implementation details.
Nowhere in the discussion have I seen any mention of what I think is the
one important item which makes DB2/400 the odd-man-out in the DB2
family:
DB2/400 exposes uncommitted changes to all users of the database.

Comments? (I am going off now to look for my asbestos underwear.)

Cheers,
Terry.

This e-mail transmission contains information that is intended to be confidential and privileged. If you receive this e-mail and you are not a named addressee you are hereby notified that you are not authorized to read, print, retain, copy or disseminate this communication without the consent of the sender and that doing so is prohibited and may be unlawful. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please delete and otherwise erase it and any attachments from your computer system. Your assistance in correcting this error is appreciated.