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 maintenance, but
Did you try with both RECONSTRUCT=YES and RECONSTRUCT=NO ?
Sometimes I have had to do that to get stubborn aggregates to move.
Also, what's the reusedelay on the pool? Sometimes resetting this can help.
Lastly, I had a lot of stuck data that wouldn't go away, and 8.1.17.100
seemed to allow
Anyone else running into connection latency on 8.1.18?
We were at 8.1.17.008 and 8.1.17.100, and came to 8.1.18.0 due to some
rollup locking patches (vs going to 8.1.17.015).
Now, we have pretty substantial hangs for client and dsmadmc connections.
During our normal backup window, it gets bad
