Hi, try this other way…..
Use the cmd <go disktasks>
select opt 1 (Collect disk space information)
in the field “when to cllect….” choose 1=date/time
in this option select *CURRENT to date and time.
Now, the system send a batch job to collect data about your entire system (information about size, %, etc)
When the job ended go again to < go disktasks >
Now select option 2 (Print disk space information)
Now you can select the better way to see your data.
Look, when you select the LIBRARY for type of report, you see the librarys in sort by size.
This is the best way to see wich library you need a little of attention….
When you select the SPECIFIC OBJECT for type of report and *FILE in object type, you see
the object (type *file) in a sort by size.
This is the other way to see wich OBJECT you need more attention, because any of this may can not be use (like savf, bkp of file).
This procedure all must be done every month. This is healthy for the system.
The above is good advice, but it might not supply enough information. It might supply much less than half of what can be needed on modern systems.
The above procedure collects information with the RTVDSKINF command and prints reports with the PRTDSKINF command. To get a full picture, there are also the RTVDIRINF and PRTDIRINF commands. (The database created by the RTV* commands can also be queried by you for any detail you need.)
Directories and streamfiles can now account for much more space usage than libraries and folders. The directory total is included in the disk totals, but the breakdowns are only available through the DIR commands.
If you schedule RTVDSKINF weekly, schedule RTVDIRINF on the same frequency.
The information needs to be collected in order to know where space usage changes. Sudden large changes can then be noticed and handled before getting out of hand.
Every object on the system takes some space. When you know where the space is used, you have a chance of controlling it.