DASD spike on a JT-Open insert? -- JAVA400-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: DASD spike on a JT-Open insert?
From: "David Gibbs" <david@xxxxxxxxxxxx>
Date: Thu, 10 Jul 2003 15:40:30 -0500
List-archive: <http://archive.midrange.com/java400-l>
List-help: <mailto:java400-l-request@midrange.com?subject=help>
List-id: Java Programming on and around the iSeries / AS400<java400-l.midrange.com>
List-post: <mailto:java400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/java400-l>,<mailto:java400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/java400-l>,<mailto:java400-l-request@midrange.com?subject=unsubscribe>

Anyone know what might cause a huge spike in dasd utilization when a jdbc
insert operation is performed?

We're using JTOpen 4.0 connected to a V5R2 system ... reasonably current on
cume and database group ptf's.

By spike, I mean the utilization went from around 75% to 99.4%!  Once the
host server job was canceled, utilization dropped down to 75% again.

Thanks!

david

-- 
David Gibbs
david@xxxxxxxxxxxx

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: DASD spike on a JT-Open insert? , 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.