Try this, it's from my AIX notes but should work..
DSMFMT an additional recovery log volume:
dsmfmt -m -log temprec1.log01 101
Use the DSMSERV EXTEND LOG command to do a recovery log extension:
dsmserv extend log temprec.log01 100
Start the TSM server. When it comes up login and disable sessions, cancel
all current sessions, and cancel all processes that may be running. Start an
incremental backup.
Once your backup is complete and the log percent utilized drops, if in
rollfoward set the log mode to normal:
set logmode normal
Then reduce the log size and delete the new log volume:
reduce log 100
delete logvol temprec.log01
Set logmode back to roll forward:
set logmode rollfoward
-----Original Message-----
From: Michael Zylberstein [mailto:[EMAIL PROTECTED]]
Sent: Thursday, April 19, 2001 1:16 PM
To: [EMAIL PROTECTED]
Subject: Full DB log file causing TCP/IP Connection Failure
I am running TSM 4.1 on Win2K and TSM is refusing all connections. I
believe I know what has caused the problem, but I am not sure what to do
about it.
The door to my IBM 3583 LTO library was left open over the long weekend and
TSM was unable to do a DB backup. As such, the log file was never truncated
and has completely run out of space. Since this has occurred, I have been
unable to make any type of connection to TSM. Whether I try to attempt with
a client, the web administrator or even the admin command line, I get a
TCP/IP Connection Problem error.
Somebody please HELP! Any suggestions would be appreciated.
Mike Zylberstein
Internet Systems Engineer, Net-Ops
Funder OnLine Corp.
[EMAIL PROTECTED]
Phone: 905-331-9105 x.277
Mobile: 416-560-0518
