RE: Strange DASD Utilization Issue

 
You did not state what OS version you are on but older versions had problems
with SQL temp indexes.
Check your system value QQRYDEGREE and only use the parm value *IO not
*OPTIMIZE or *MAX.

P.s
Just last week I got a call that a clients machine was going over 90% DASD
usage.  Found they had a work file that had over 1.8 million deleted records
(no active records) consuming 60+ Gig.  To make this even worse they had
saved the file to a SAVF so they doubled the bad hit.  The fix was quick and
they are sooo happy now at 43%.

--
Doug Hart
 
 

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of DebbieKelemen
Sent: Monday, February 27, 2006 5:58 PM
To: 'Midrange Systems Technical Discussion'
Subject: Strange DASD Utilization Issue

I need some help trying to figure out a DASD utilization issue that is
plaguing me.

After an IPL, my system is at a nice 38.64% utilization.  Within a day it
has grown to 42.98%.  I can guarantee within a few weeks I will be up to 50
or more percent and I will need to IPL to get my DASD down for the mid 60%
within a 6 week period or so.

When I run a GO DISKTASK, it shows that Temporary space is 5% of my system.
That is what my system grew by.  How do I keep my temporary space under
control?  

Debbie


--