Re: Default isolation levels for remote connections -- MIDRANGE-L

Subject: Re: Default isolation levels for remote connections
From: CRPence <CRPbottle@xxxxxxxxx>
Date: Sat, 23 Aug 2014 08:51:41 -0500
List-archive: <http://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

On 22-Aug-2014 13:56 -0500, Matt Olson wrote:

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...

No harm in asking IBM support, I suppose. Though I will note, that using the getTransactionIsolation to inquire of the setting rather than inferring something from server-job attributes should be more accurate. There is no requirement that a server job must have any particular level of a [job-scoped or activation-scoped] commitment control [or no CmtCtl] established, to manage\effect a particular isolation-level implementation for the client.

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2025 by midrange.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 on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.