Hi,

we saw nearly the same on upgrade from 5.1.6.3 to 5.2.1.1 on MVS.
Upgrade went fine, but after start of the server with the new version TSM 
starts a process which you cannot see with "q proc", uses lots of CPU, doesnt 
respond to MVS modify commands and lags with the AdminGUI.
With the help from support we saw that the server starts an cleanup 
backupgroups after restart with 5.2.x.x.
This process cannot be cancelled and uses the CPU a lot.
Now we decided to go to 5.1.7.3 to use the cleanup backupgroups by our own (so 
we are able to stop this process if we need the CPU for backups/archives).

btw: Take a look at PQ78408: ...ITSM Server V5.2 is modified to detect and 
correct the incorrect backup group entries during UPGRADEDB processing...

regards,
Joachim Stumpf