Spool file analysis
Is there a way to Calculate the disk space I would get back if I use the TAATOOL cmd DLTOLDSPLF? I need to find the difference between using 90 days vs. 120 days in the command. I currently have one system that has the following infor for spool files:
11/02/07 14:26:54 Display Spool Size - TAA
Total members - 292,630
Empty members - 4,783
Data members - 287,847
Total size - 116,074,975,232
Empty size - 78,225,408
Data size - 115,996,749,824
QSPL library - QSPL
Thanks, Bruce
Software/Hardware used:
Software/Hardware used:
ASKED:
November 2, 2007 8:24 PM
UPDATED:
October 29, 2009 4:25 PM
Answer Wiki:
Note that, in general, deleting spooled files isn't what recovers the space. Space is recovered by running RCLSPLSTG (Reclaim Spool Storage). Also, you didn't say anything about your environment such as OS version/release. Also, you only showed output from a TAATOOL command with no info from system commands for comparison.
If this is DLTOLDSPLF from TAATOOL and "Display Spool Size -- TAA" is also a TAATOOL command, then only TAATOOL support can answer with much certainty.
However, if you're intending to cut the retention period from 120 days to 90 days, I'd guess that you could perhaps recover around 27GB... assuming you reclaimed spool storage after spooled files were deleted.
Personally, I doubt that I'd be allowing spooled files to stay around much more than 30 days. The purpose of spooling a report is to print it. A spooled file is not for long-term storage -- that's what the paper is for (or the .PDF or whatever).
You might investigate the EXPDATE() and DAYS() attributes of spooled files in V5R4 and later. And also look at Delete Expired Spooled Files (DLTEXPSPLF) in V5R4.
Tom
To see all answers submitted to the Answer Wiki: View Answer History.
I agree with Tom. You are taking up way to much space on the system with spool files. We use the DLTOLDSPLF command from TAATOOL as well. In our program we use that command across the whole system using specifying the RETAINDAYS of 30, but we only exclude a handful of output queues from that, which in effect prevent critical output queues from ever being touched. Then, there are several others that we run the command individually on, specifying number of RETAINDAYS…. 2, 4, 7, or 14. We’ve done this for several years and it’s kept the amount of space spool files take up to just a few gig.
Bruce #2