> Thanks Richard for your answer howevere we are running Windows port 
> of TSM 5.3 and the dsmfmt is not supported,

It is most certainly supported. You will find it in the ..\TSM\console 
directory. You can also use the TSM Management Console to format a 
recovery log volume.

Check your documentation, in particular the TSM Administrator's Reference, 
Appendix A.

> we are having difficulies in getting the correct syntax of the
> "dsmserv format" and is not behaving as expected.

That is good, since Richard's response was absolutely correct: Assuming 
you still want to recover from the "out of log space" condition, running 
"dsmserv format" will put you in a world of hurt. Read the description for 
that command (also in the Admin Reference, Appendix A) and you will see 
that it formats not only the recovery log, but the database, too. What you 
want is to format a new recovery log *volume*, not the whole recovery log 
and database. In short, you don't want "dsmserv format".

The TSM Administrator's Guide has a section that discusses recovering from 
the out of log space condition. See the chapter on "Managing the Database 
and Recovery Log", section "Increasing the Size of the Database or 
Recovery Log", sub-section "Recovering When the Recovery Log Runs Out of 
Space".

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 2005-03-14 
19:21:02:

> Thanks Richard for your answer howevere we are running Windows port 
> of TSM 5.3 and the dsmfmt is not supported, we are having 
> difficulies in getting the correct syntax of the "dsmserv format" 
> and is not behaving as expected.
> 
> Thanks
> 
> Carl
> 
> ---- Richard Sims <rbs AT BU DOT EDU> wrote: 
> > Carl -
> > 
> 
> > 
> You should NOT be using DSMSERV FORMAT to create additional Recovery 
> > 
> Log space: use the DSMFMT command. You're lucky that the command 
> > 
> failed! Refer to the Admin Guide manual topic "Recovering When the 
> > 
> Recovery Log Runs Out of Space" for the steps to follow. And by all 
> > 
> means review server configuration and maintenance topics in that manual 
> > 
> to avoid major problems like this.
> > 
> 
> > 
>    Richard Sims
> > 
> 
> > 
> On Mar 14, 2005, at 5:42 PM, Carl Lea wrote:
> > 
> 
> > 
> > ANR9999D adminit.c(1530): ThreadId<0> Insufficient log space to update 

> > 
> > table
> > 
> > Administrative.Attributes.
> > 
> > ANR9999D ThreadId<0> issued message 9999 from:  <-105642D8 
> > 
> > outDiagf()+168
> > 
> > <-1005EA24 admInitPart2()+13c4
> > 
> >
> > 
> >
> > 
> > I suspect the log space is full.....
> > 
> >
> > 
> >> From what I can tell I need to format some space for the log file 
> > 
> >> then extend the log... simple right...
> > 
> >
> > 
> > This is what I get when attempting to format a log file?..
> > 
> >
> > 
> > :\Program Files\Tivoli\tsm\server>dsmserv format 1 c:\new_log.dsm 25mb
> > 
> > NR0900I Processing options file C:\Program 
> > 
> > Files\Tivoli\tsm\server\dsmserv.o
> > 
> > .
> > 
> > NR7800I DSMSERV generated at 17:33:50 on Dec  7 2004.
> > 
> >
> > 
> > ivoli Storage Manager for Windows
> > 
> > ersion 5, Release 3, Level 0.0
> > 
> >
> > 
> > icensed Materials - Property of IBM
> > 
> >
> > 
> > C) Copyright IBM Corporation 1990, 2004.
> > 
> > ll rights reserved.
> > 
> > .S. Government Users Restricted Rights - Use, duplication or 
disclosure
> > 
> > estricted by GSA ADP Schedule Contract with IBM Corporation.
> > 
> >
> > 
> > NR4726I The ICC support module has been loaded.
> > 
> > issing format arguments.
> >