Start with
        dsmfmt -log name of new logvol -g #ofbytes  (check the manual to
see if I have this in the right order)

When the format is thru
        dsmserv extendlog new logvol #of bytes  (check the manual to see
if extend is one or two words)

When the log is defined bring up the system as normal.

We have found that it is better to never let the log exceed 10-11 Gb when
the system is in rollforward mode.  Even if we have a log full situation in
the middle of the night, the above procedure takes minutes and the system
is up and going.  Then we delete the new logvol at the first chance.  If
the full 13 Gb is allotted to the log and it fills, the solution is to
restore the DB.  In our case, that's 150 Gb and hours of down time.


At 09:48 AM 7/9/2004 -0500, you wrote:

About 4AM this morning, it appears that my TSMseverer (windows 2K, TSM
server 4.3) won't start.

I try starting the sever in a console window and it tells me that the log
files are over full.
How can I add another log file and format it without having the server
start?

(the log files I watch daily and have never been over their high water mark
of about 78% full,
and I have 6G allocated for a database of about 30G)

Suggestions? ...

Fred Johanson
ITSM Administrator
University of Chicago
773-702-8464