|
Jeff, I had a similar problem, yet on a smaller system at V4R5. Customer "lost" about 2 GB of DASD space per day. I searched high and low, we even had calls to IBM and investigated together with them and some PEX-tools and so on, nothing ! Then I simply did stop server-jobs, one after each other. I found out that stopping and restarting the netserver-job immediately freed up that space so we included this in a scheduled routine job for the night. ;-) Never solved the cause of this, though. When we finally went to V5 the problem disappeared.
HTH, Philipp
-- *** Vicker Programming and Service *** Have bits will byte *** www.vicker.com *** Don't sweat the petty things, just pet the sweaty things.
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.