|
If you are going to run RTVDSKINF you might as well run it in a single
string job queue and run
PRTDSKINF RPTTYPE(*SYS)
in the same job queue. It's a small summary report.
While queries on the files generated by RTVDSKINF are useful, to assume
that the problem are with traditional DB2 files, journals, etc is a big
mistake. Our IFS objects make our DB2 objects look puny.
Besides, if it's in some really esoteric object then that is more likely
to show up on the *SYS report.
You could get really weird. Let's say you have some paging software that
acts upon a message in a message queue. Then just create the message
queue QSYS/QSYSMSG. Change your threshold down to some safe percentage,
like 80%. When that is exceeded, and your software catches the message in
QSYSMSG then it can act upon it.
If you page, then don't use email. Use a modem instead. Exceeding
threshold has a tendency to shutdown some tasks and I believe email is
one.
Rob Berendt
--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
Benjamin Franklin
"Burns, Bryan" <burnsbm@xxxxxxxxxxxxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
10/13/2003 02:17 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
To
"'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
cc
Subject
RE: something using up DASD
I had a similar situation on our 820 with 120G of DASD where overnight 1G
or
so would be used up and I could not trace it down. I finally solved it by
running RTVDSKINF on daily at 2:00 a.m., along with a query (scheduled
several hours later) that lists ALL OBJECTS over 100mb sorted by size.
RTVDSKINF creates a file, QAEZDISK, over which the query runs.
This procedure is very useful if ran daily as indicated. The culprit in
my
case turned out to be an object called *INTSYSJRN. This object can grow
really fast overnight. It's less than a MB today but was over 1.2G just
last week.
For what it's worth, below is a snip from my query of QAEZDISK that ran
this
morning.
Object Object Text Description
Object Object Object Last
Size
Type Library Owner Used
Date
*TDSKSPC 120,259,084,288
*SYS
*UNUSED 40,219,246,592
*SYS
IMHIST 6,807,474,176 Inventory transaction history file
FILE AMFLIBE AMAPICS 031013
$PRDRGH 1,477,570,560 Product Registration Header File
FILE AMFLIBE ROBM 031012
MOHDTA 1,345,904,640 Order history-component detail
FILE AMFLIBE AMAPICS 031010
$LPND 986,353,664 License Plate Detail
FILE AMFLIBE ROBM 031011
*VLICOTHER 985,243,648
*SYS
MBDDREP 929,099,776 Shipment release physical file
FILE AMFLIBE AMAPICS 031013
*TMPSPACE 888,909,824
*SYS
IMHIST01 777,015,296 Inventory transaction history logical
FILE AMFLIBE AMAPICS 031012
OEITXN 713,076,736 COM-transaction file
FILE AMFLIBE AMAPICS 031010
MBGFCPP 655,409,152 Historical tax physical file
FILE AMFLIBE AMAPICS 031012
*JOB 649,271,296
*INT
AMBSRC 616,349,696 Customer Order Management Source
FILE AMMLIBU QDFTOWN 030925
Hope this helps.
-----Original Message-----
From: Rubino, Jim [mailto:Jim.Rubino@xxxxxxxx]
Sent: Monday, October 13, 2003 12:58 PM
To: 'midrange-l@xxxxxxxxxxxx'
Subject: something using up DASD
Since we upgraded our operating system from V4R5 to V5R2.........our DASD
used keeps on climbing. Can anyone tell me where to look for files that
the
system maybe using that can be cleared? Is there something running that
we
do not need to be running that is using up disk space? This is on an
ISeries 730, we have 154.6G of DASD and currently 92.2575 % is used up.
This machine is our development machine we only do programming mods and
changes on this machine with some users doing some testing. This machine
is
almost a mirror of our production machine for data. When we left on Friday
it was just under 90 % and I has increased from 91.0118 % this morning.
Any
help anyone can give on where to look would be greatly appreciated.
TIA
Jim Rubino
Senior Business Systems Analyst
FIKE CORPORATION
704 South 10th Street
Blue Springs, Mo. 64015
(816) 229-6216 Ext. 213
_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.