Re: V5Rx Nuances -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Re: V5Rx Nuances
From: "M. Lazarus" <mlazarus@xxxxxxxx>
Date: Sat, 07 Dec 2002 20:58:40 -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/cgi-bin/listinfo/midrange-l>,<mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/cgi-bin/listinfo/midrange-l>,<mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Bill,

At 12/6/02 05:30 PM, you wrote:

they changed all of the Access path size from *MAX4G to *MAX1TB in all
keyed files and logicals files, they were told by IBM to do this because
the data from some database monitor jobs showed high contention for keys.

What has been your experience with these two issues?

 I know of a shop that did the access path change en masse and experienced
*terrible* performance degradation.  EVI's are only better in certain
circumstances.  It is not an across the board panacea.

 -mark

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: V5Rx Nuances , Joe Pluta

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.