Thanks for the reply. We have run REPAIR OCCUPANCY numerous times now and
it has "adjusted" total reporting occupancy by* -100TB*. This is very
concerning since our IBM license is storage/TB based and 100TB makes a lot
of difference/required us to increase our license.
On Sat, Apr 22,
I mean, it's formally in a whitepaper from 2018,
https://www.ibm.com/support/pages/repair-occupancy-repair-reporting-occupancy-storage-pool
and dsmserv was updated in 2021 to allow this to run on a container pool.
https://www.ibm.com/support/pages/apar/IT15373
It's not normal mainte
Linux Server 8.1.14.200
Looking for feedback on this "undocumented" (i.e. not in a book but readily
available via Google search) command.
We have been seeing lots of wacky occupancy numbers, issues with nodes
reporting something in stgpools that are empty, etc. I stumbled upon
REPAIR
