Thanks. I think the reason why EXPIRE INVENTORY without NODES only seems to expire a small amount of nodes is that it tries to continue where it left the last time it stopped – if you happen to normally run expire with DURATION=<minutes> limitation. If TSM cancels the expire process after duration is exceeded, it does not emit any errors or warnings (unlike ANR4927W for reclamations) to the activity log, so this can easily go unnoticed for few days unless there is a specific monitoring for slow expires in place.
On Thu, 2016-11-10 at 14:59 -0500, Zoltan Forray wrote: > Here is the 6.3.6.000 expiration problem APAR description: > > IT17642: SLOW EXPIRATION AFTER UPGRADE TO 6.3.6.000 SERVER > > APAR status - OPEN - > > *Error description* > After upgrading the server to 6.3.6.000 (or higher) and 7.1.3(or higher) > expiration might "hang" on a node while expiring backup data only. > Expiration is not actually hung it is still processing but very slowly due > to a non-optimized SQL/Select. A change to this SQL/Select occurred > between 6.3.5.0 and 6.3.6.0. This code change was implemented in servers > 6.3.6.0+ and 7.1.3.0 to 7.1.7. There have been no reported problems at > 7.1.3 or above.
