MIDRANGE dot COM Mailing List Archive

RE: Default isolation levels for remote connections


We attempted to set the DefaultIsolationLevel to CHAOS (no commitment control) and looked at the QZDASOINIT jobs on the server and they were still getting created with *CS.

Probably have to open a case with IBM to see whats wrong...

-----Original Message-----
From: CRPence [mailto:CRPbottle@xxxxxxxxx]
Sent: Friday, August 22, 2014 9:40 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: Default isolation levels for remote connections

On 21-Aug-2014 14:32 -0500, Matt Olson wrote:
Does anyone know what the default isolation level is for remote
connections to the IBM i via DRDA that don't specify any isolation
settings in the connection string?

Serializable? Repeatable Read? Read uncommitted?

I am unsure of what relevance there is to a /connection string/ and the DRDA, but AFaIK the default isolation for a DRDA connection is Read Uncommitted [aka COMMIT(*CHG)] for a DRDA CONNECT request; consistent with the Commitment Control (COMMIT) parameter defaults for the various SQL pre-compiler and run\scripting features [other than Start SQL Interactive Session (STRSQL)].

For an interface that uses a /connection string/ implementation, such as JDBC, the default transaction isolation level is defined by the particular implementation being utilized. For example, with the IBM i Access ODBC connection string, the default transaction isolation level is "2 = Read uncommitted (*CHG)". For the JDBC there exist features to retrieve and set [both the auto-commit setting and] the isolation so what is defaulted could be immaterial if checked and set; those features could be utilized to [re]establish the desired settings blindly, or perhaps the SQL statement to SET TRANSACTION ISOLATION LEVEL would suffice [if the auto-commit setting is not also of interest].?

Regards, Chuck
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.

Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2015 by MIDRANGE dot COM and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact