|
run RTVDSKINF as a bench mark - rename QAEZDISK in QUSRSYS, then run RTVDSKINF at a later time/day. Query both files, or print the disk info reports against both to see where your growth is. If it's in temporary space, an IPL will recover it, as you discovered, although it _SHOULD_ come back when a job no longer needs it or ends. If you have the time you could find the culprit job(s) that is/are eating up temporary space by a process of elimination. End jobs one by one till you see a lot of temp space come back. If so, that job is the one. If it's in internal system objects, create a data area in QUSRSYS named QEZDMPINTL TYPE(*CHAR) LEN(1). It's intended for IBM to see what type of internal objects are using the space. If you poke around in the QAEZDISK file you might see that info your self. Anyway, the difference between the two RTVDSKINF runs should tell you where your space is going. (Don't leave the QEZDMPINTL data area there - it makes your RTVDSKINF run longer & generate a LOT of data.) HTH Alex > > I did a release upgrade on a V4R4 machine (a 720) to V4R5 > in november last > > year. > > We were at about 50% used disk space at that time. PTF > package C0198450 > > was > > installed at that date as well, everything went fine. > > Since we did not do any further IPLs since then, we someday > noticed that > > something > > is eating up disk space, until we reached 92 % last week. > > Searching for the culprit was at no avail, we ended every > user jobs, ended > > every non-system > > job on the system, it eats space on and on. A short > calculation led us to > > round about > > 300 MB (!) temporary space which is used up every day since > november. > > WRKSYSSTS showed 29 GB of temp used space out of 77 GB > total, this is 38 % > > of the > > whole system ! > > When we scheduled an IPL to get rid of the temporary used > space, I did > > endsbs *all *immed > > at first hand and suddenly all our used disk space was free > again ! You > > could watch it coming > > back available when pressing F5 in wrkssysts display. I > never saw this > > behaviour on an AS/400 > > before. IBM support was nearly as helpless as we, we > ordered some PTFs > > that might help ... > > > > Any hints anybody ? > > > > Have a nice easter weekend, > > regards from germany, Philipp Rusch > > > > _______________________________________________ > > This is the Midrange Systems Technical Discussion > (MIDRANGE-L) mailing list > > To post a message email: MIDRANGE-L@midrange.com > > To subscribe, unsubscribe, or change list options, > > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > > or email: MIDRANGE-L-request@midrange.com > > 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@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > or email: MIDRANGE-L-request@midrange.com > 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.
midrange.com
