|
midrange.com
And here is a sample from my IFS:
DIR OBJ Total size
/QFPNWSSTG/GDSNT3 QFPCLTSTG1 67,110,060,544
/QFPNWSSTG/GDSNT6 QFPCLTSTG1 53,686,403,584
/QOpenSys/usr/tivoli/tsm/serve backup.dsm 52,428,800,000
/QOpenSys/usr/tivoli/tsm/serve stgvol.001 52,428,800,000
/QOpenSys/usr/tivoli/tsm/serve stgvol.002 52,428,800,000
/QFPNWSSTG/HELPSERV3 QFPCLTSTG1 42,952,413,184
/QFPNWSSTG/GDSNT4 QFPCLTSTG1 26,847,314,944
/QFPNWSSTG/GDSNT5 QFPCLTSTG1 26,213,968,384
/QFPNWSSTG/GDSTNG33 QFPCLTSTG1 22,545,493,504
/QFPNWSSTG/GDSNT7 QFPCLTSTG1 11,811,503,104
/QFPNWSSTG/GDSTNG14 QFPCLTSTG1 10,742,216,704
/QFPNWSSTG/GDSTNG13 QFPCLTSTG1 10,733,991,424
/QOpenSys/usr/tivoli/tsm/serve dlog.002 8,389,656,576
/NOTES01/NOTES/DATA/mail dhayes.nsf 4,110,417,920
/GDDATA/NOTES/DATA DocImgs.nsf 3,724,279,808
/NOTES01/NOTES/DATA/mail glaukhuf.nsf 3,670,540,288
/QUALITY/NOTES/DATA/QUALITY23/ ecreco.nsf 3,127,902,208
/NOTES01/NOTES/DATA/mail mdray.nsf 2,624,323,584
/GDDATA/NOTES/DATA WebImages.nsf 2,513,436,672
Just three off the shelf IBM packages: IXS, TSM, Domino.
Here's a shot from my DB2
Library Object SIZE
PCBACKUP PCBACKUP00 262,209,286,144
PCBACKUP PCBACKUP01 262,209,286,144
PCBACKUP PCBACKUP06 104,884,985,856
PCBACKUP PCBACKUP07 52,447,748,096
PCBACKUP PCBACKUP11 52,447,748,096
PCBACKUP PCBACKUP12 52,447,748,096
PCBACKUP PCBACKUP13 52,447,748,096
PCBACKUP PCBACKUP14 52,447,748,096
PCBACKUP PCBACKUP02 52,443,553,792
PCBACKUP PCBACKUP03 52,443,553,792
PCBACKUP PCBACKUP05 26,224,934,912
PCBACKUP PCBACKUP10 26,224,934,912
PCBACKUP PCBACKUP04 26,222,837,760
PCBACKUP PCBACKUP09 20,990,439,424
PCBACKUP PCBACKUP08 10,504,667,136
PCBACKUP DB00 7,866,449,920
ROUTINES IFSLIST 6,771,703,808
MGR1499099 PRTRAND 4,260,417,536
QMPGDATA Q276000008 3,500,879,872
QMPGDATA Q281000140 3,360,501,760
QMPGDATA Q279000137 3,314,233,344
QMPGDATA Q280000009 3,289,067,520
QMPGDATA Q275000142 3,228,250,112
QMPGDATA Q278000009 2,888,388,608
QMPGDATA Q277000004 2,837,098,496
CLOCFILE00 CKAUDITF 2,222,043,136
EDI4XXDTA EDUSER 2,104,025,088
CLOCFILE00 CKFMTHST 1,909,792,768
MGR1499099 PMLICLPD 1,696,936,960
BACKFILE00 CKFMTHST 1,653,723,136
CHRIS PVCTEST 1,556,484,096
QSYS QADBIFLD 1,433,587,712
CLOCFILE00 CKTIMEFL 1,399,431,168
MAX DHTDIVFSF 1,179,664,384
BACKFILE00 CKAUDITF 1,174,458,368
QUSRSYS QAYPSLOG 1,102,630,912
QMPGDATA Q282000007 1,071,992,832
PCBACKUP LOG02 1,050,697,728
BACKFILE00 CKTIMEHS 1,023,758,336
LYLDIVF ITH 944,340,992
Oh, and when we upgrade wholly to the new TSM you can skip anything in the
library PCBACKUP. That will go into the IFS. That really tilts the
scales, doesn't it?
IFSLIST is the hysterical, (pun intended) file that keeps track of our IFS
growth.
The last file shown is the first file to appear from our ERP system. Other
than a few payroll files in there the rest is performance data, errant
save files, etc.
Ok, so we've got email files that almost exceed our biggest DB2
application file. (That engineer's picture is on our web site.)
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-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.
