


...with all these catered for should I be looking at something around 75% or say 50%?
With "all those catered for", I have no problem thinking of 50%-75% as a good healthy range. Whether it should be closer to 50% or 75% will depend on the metrics for "all those" and a couple others.
I've worked with systems that had no problems at 95+%. But I have no idea what your values are for "optimum performance / cost". Nor do I have any idea what performance tuning has been done on your systems, nor what your workload profiles are, nor the volitility of your database, nor the prevailing access methods, nor any factors such as journaling/commitment control, nor...
Given what's known, I don't think there's any good way to get closer than a guess of "50%-75%" for "optimum performance / cost". It's as good a guess as any.
Tom
First thing to do is find out what is take up space on the disk. The more we have, the more we collect data. Sometimes a good cleanup can reduce disk utilization by 10 to 30%.
Next you need to set policies on file retention.
Now that your system is clean, if you are at 80%, you should have ordered more disk and be waiting to put it in.
If you are running below 70% you should be OK.


one of the ways is to like draft a chart on how fast the DASD is taken then from there you can kinda guess how much u need. last time i too work with a system with about 90-95% but it work fine, but like Tom say it depends on the values that you have set. to me 50-75% is also a healthy range.
Thanks for the answers guys; I’ll close this topic now. I do have systems running at 90% and I also have system running at 50%.
One observation I have made is that the higher the % the more clean up both Apps and Infra do! Yes it is driven from necessity but still carried out more frequently, I find it very difficult to get my apps guys to archive or clean up when we are closer to 50% even after providing them with reports naming and shaming.