In regards to Neil Poland's response, I've had to do the same thing
recently.  The only difference is that I did a FULL backup of the database.
Also, after I reduced the log back to it's original size, I left the new log
volume (in Neil's example - "temprec.log01") out there in case I ever needed
it again.

It's a pain in the backside, but it will work.

Good luck,

Jeff Caffey
Enterprise Systems Programmer
(AIX & Storage Administrator)
Pier 1 imports, Inc.  -  Information Services
jlcaffey AT pier1 DOT com
Voice: (817) 252-6222
Fax:   (817) 252-7299

 -----Original Message-----
From:   Poland, Neil [mailto:NPoland AT TTIINC DOT COM]
Sent:   Thursday, April 19, 2001 1:48 PM
To:     ADSM-L AT VM.MARIST DOT EDU
Subject:        Re: Full DB log file causing TCP/IP Connection Failure

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