Mark,
We had this issue a few weeks ago.  We ended up having to get Tivoli
level2 to walk us through the fix.  It basically involved finding a
filespace (we use AIX for server) that had spare room, defining a
temporary log volume using the dsmserv command, and letting it use this
"extra" space to perform the redo action.  Sorry this is short on
detail, maybe one of the tsm "gurus" can fill in the exact commands?

-----Original Message-----
From: Hokanson, Mark [mailto:Mark.Hokanson AT WESTGROUP DOT COM] 
Sent: Tuesday, January 07, 2003 3:19 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: HELP: MVS TSM Server Hanging on Boot


This morning we noticed our TSM recovery log was ~97-100% full. The
server was still up but we couldn't log in. We halted the server,
increased the recovery log, and are trying to bring the server back up.

The problem is the server is stuck in Recovery log undo pass in
progress.

10.36.06 STC24351  ANR0900I Processing options file dsmserv.opt.

10.36.07 STC24351  ANR0990I Server restart-recovery in progress.

10.36.30 STC24351  ANR0200I Recovery log assigned capacity is 11780
megabytes. 10.36.30 STC24351  ANR0201I Database assigned capacity is
53728 megabytes.

10.36.30 STC24351  ANR0306I Recovery log volume mount in progress.

10.44.07 STC24351  ANR0353I Recovery log analysis pass in progress.

11.57.38 STC24351  ANR0354I Recovery log redo pass in progress.

12.52.38 STC24351  ANR0355I Recovery log undo pass in progress.

12.52.40 STC24351  ANR0362W Database usage exceeds 88 %% of its assigned
capacity

Can anyone please advise?

Mark Hokanson
Thomson Legal and Regulatory