Re: (changed) DASD usage of IFS objects

----- Original Message -----
From: "rich herdman" <rherdman@columbus.rr.com>
To: <midrange-l@midrange.com>
Sent: Friday, January 04, 2002 10:34 AM
Subject: (changed) DASD usage of IFS objects
> Maybe that would explain our problem - our DASD usage is growing at
> (almost) alarming rate since we went to V5R1, and we have been running
daily
> DSPLIB's to find the culprit(s).  We have been unable to find any
libraries that
> are growing that fast, but we do have a bunch of stuff (spread evenly
between
> lots of little files and a few large files) we put into the IFS on a daily
basis.

one area that I noted an extreme increase of DASD usage was the performance
collections. After going to 5.1 (from 4.3), one of my customers experienced
the same sort of thing. In a one month period of time, 12G in performance
collections.

while I have not explored this thoroughly yet, the performance collections
are turned into performance members for PM400 and the tools reports, and the
collections also stayed on the system. It also appears that someone had
turned on ALL in the collection, so it collected a lot.

we deleted them and turned it way down on the collection and things seem
much more normal now....

don't know if you have this too, but it's worth looking at. the go disktasks
will report these objects too.

===========================================================
R. Bruce Hoffman, Jr.
 -- IBM Certified Specialist - iSeries Administrator
 -- IBM Certified Specialist - RPG IV Developer

"I want to be different, just like everybody else!"
  - Ceili Rain