The resolution of this was that after 3 1/2 hours the UPGRADEDB process was still getting time, but there was no dsmserv.err file, and given other indicators, TSM Support made an educated guess and recommended that I kill it and start dsmserv. That was successful. We are now on release 5.5.4.1.
Best wishes, Keith Arbogast
