From: ADSM: Dist Stor Manager on behalf of Choudarapu, Ramakrishna (GTI)
Looks like this pin is 'stubborn', as the successful completion of the
database backup for last three days, did not clear the log. AFAIK, this
has not happened before.

What would happen to the uncommitted transactions if the TSM service is
recycled?

[SNIP]

Can't say, although I've never lost any TSM db data when forced to run HALT on 
the server; I suspect that forces a log commit as part of an orderly shutdown.

If you've got time, I'd log a call with Tivoli support and set a ticket for 
this. They may want to gather some data on the situation, time and your 
situation permitting. This is the first "stubborn" log pin with no obvious 
cause I've heard of since 5.3 came into being.

What size is your recovery log?

--
Mark Stapleton (mark.s AT evolvingsol DOT com)
Senior consultant