Mark,

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?

Regards,
Rama

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Mark Stapleton
Sent: Wednesday, February 07, 2007 12:12 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Recovery Log Pinned


From: ADSM: Dist Stor Manager on behalf of Choudarapu, Ramakrishna (GTI)
We had a recovery log pinning problem and the log was growing since last
4 days and currently is at 72% util... TSM Server 5.3.3.0 running on
z/OS. Below is the SHOW LOGPINNED output:

(snip)

It looks like you're currently running a database backup; that should
clear the log unless the pin is stubborn.

If the db backup doesn't clear up your problem, you may want to consider
taking the TSM service/process down and then restarting it.

Has this happened before?

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

If you are not an intended recipient of this e-mail, please notify the sender, 
delete it and do not read, act upon, print, disclose, copy, retain or 
redistribute it. Click here for important additional terms relating to this 
e-mail.     http://www.ml.com/email_terms/
--------------------------------------------------------