|
There are some WRKSYSVAL values and GO CLEANUP settings that can be adjusted.* After someone deletes a report, how long is the disk space available to spool file, and how fast is it recovered? * There's values you can muck with for performance, or just let the system calculate for you, given several alternative game plans that you can setup, such as what happens at IPL time, through GO POWER schedule?
Depending on how some application software accesses some files, there is a trade off between getting at the records most recently added to end of file, and finding through the index. Look at the amount of disk space eaten by a volatile physical file that has a ton of logicals. The aggregate of the logicals could exceed the physical disk space, and all of them being updated every time change physical. This can be a drain. But the application probably comes with some kind of reorg support.. For some volatile files it can be more efficient to soft code records for deletion, then hard remove at a time when not a lot of folks on the system. Plus many files designed with growth space disk grabbed, so as the file grows, it not have to grab disk space from other, so you not get the fragmentation typical on other OSs.
I'm a fossil and have been around since 360/20 days. Other than using RGZPFM to re-organize some very volatile file on my career long boxes, I just realized that I've not thought about or worried about defragging the drives as a whole. I revitalized some of my grandkids laptops this last weekend by simply defragging them. The question of why we don't need to do that on the Iseries boxes popped into my head. Is that because the don't need to have it done, or we really do need to do that and is it like the early days when IBM just didn't give us the same tools and features that existed on other boxes. That's not necessarily a complaint because I think many may have stayed out of trouble by not having some more esoteric features available. There is also the issue that they write books about what I don't know about that which I work on. [grin] Steve Moland -- 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.