Re: Automatic deadlock detection -- MIDRANGE-L

Subject: Re: Automatic deadlock detection
From: CRPence <CRPbottle@xxxxxxxxx>
Date: Wed, 12 Jan 2011 11:34:46 -0800
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/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

On 1/12/11 11:14 AM, dieter.bender@xxxxxxxxxxxx wrote:

... I don't know what's the condition for DB2 LUW, for db2/400 you
have to have in mind:
- default for the record wait is 60
- default for a table wait is 0 (they must have smoked something
good)
<<SNIP>>

Actually since V5R3 [apparently per http://archive.midrange.com/midrange-l/200704/msg00373.html I recall the change, not the date\rls] the default for WAITFILE is 30 seconds and the default for WAITRCD is 60 seconds, and since some PTF level in the V5 releases, the default for both of those values come from *SYSLIBL/CRTPF such that the values are customizable with CHGCMDDFT.

http://www-912.ibm.com/s_dir/slkbase.NSF/0/4c7e1e2f94136bdd86256c6200577243?OpenDocument

Regards, Chuck

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2024 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.