|
A few weeks ago we went from V4R3 to V4R5 & with some trepidation I looked at disk space consumption before & after. We are on a 12 Gig model 170 & I asked the rhetorical question "If V4R5 is going to eat 5% more of disk space, what will V5R1 eat?" Then the next day I was annoyed to see disk space went down by another 5%, ditto the next. Well it has stabilized now, but I have been running IPLs much more frequently than in the past, and tackling some disk space wastage issues in applications where previously I did not feel motivated to spend the time at cleaning up what might be marginal. Now I feel happy if I have saved 0.05 % disk space after a large chunk of my time futzing with stuff, because the disk space consumption is unhealthy. My theory ... is that V4R5 needs to convert some of our stuff to a new format that eats more disk space, but it does not do the conversion until we actually use it. I had seen references to this in various past threads with respect to: What all information baggage is carried along with a spool file report; What all is in a file external description that can make SQL more efficiently access it & also provide capabilities for new kinds of file ingredients; System indexing that can make SQL & other access methods more productive, at the cost of eating more disk space. Also perhaps temporary PTFs are eating more disk space than we realized. Buying another hard drive is not an option as far as management is concerned. MacWheel99@aol.com (Alister Wm Macintyre) (Al Mac)
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.