Hi Wanda, try www.ibm.com and searching on:
+"repair stgvol" +tsm
to find some hits.
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/[email protected]
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.
"Prather, Wanda" <Wanda.Prather AT JHUAPL DOT EDU>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
Please respond to
"ADSM: Dist Stor Manager"
ADSM-L AT VM.MARIST DOT EDU
Re: Flash 10282 has been published
Well I'm confused. I can't find REPAIR in the 5.2.2 admin guide or admin
Anybody know what it is/how to use it?
From: Sam Giallanza [mailto:giallanz AT US.IBM DOT COM]
Sent: Tuesday, April 20, 2004 1:15 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Flash 10282 has been published
TSM Community :
Flash 10282 has been published:
Including the Flash text below :
Abstract: TSM Server can not be restarted after running REPAIR STGVOL
utility in 220.127.116.11 or 18.104.22.168, if a volume is not
specified when the command is issued.
Problem: The REPAIR STGVOL utility shipped with TSM 22.214.171.124 and TSM
may alter the TSM Server Data Base and prevent
the TSM Server from being able to be restarted.
Who is Affected: TSM servers, on which REPAIR STGVOL has been run without
specifying a volume for the utility to repair.
I.E. if this utility is run without specifying any parameters, then the
symptoms referenced in PQ86959 will be experienced.
TSM Servers affected by this problem will not notice the damage until the
TSM Server is stopped and then attempted to be
restarted, so it is possible to run with the damage to the Data Base for
some time before the problem will be encountered.
The fix for PQ86959 is targeted to be fixed in levels 126.96.36.199 and 188.8.131.52
of the TSM Server which should be available by
May 24, 2004.
If this utility must be run, a volume MUST be specified. If possible do
use this utility until the fix for PQ86959 is
available. Here is the information from the APAR;
REPAIR STGVOL utility provided with IC37275 in 184.108.40.206 can
corrupt the server database and prevent the server from being
restarted. If the utility command is entered without specifying
a specific volume it will create an AS.Volume.Status entry for
disk storage pool volumes that will cause abend0C4 during server
ANR9999D Trace-back of called functions:
ANR9999D 0x000000010093D118 AsVolRestart
ANR9999D 0x00000001009281B4 AsInit
ANR9999D 0x0000000100978118 ssInit
ANR9999D 0x0000000100163BD0 admStartServer
ANR9999D 0x0000000100055028 main
ANR9999D 0x00000001000525BC _start
ANR9999D 0x0000000000000000 *UNKNOWN*
Do not use the REPAIR STGVOL utility
without specifying a volume.
Crash dump signal sig 11 segmentation violation
If this problem is encountered a point-in-time(PIT) DB
restore will need to be done to a PIT prior to when the
REPAIR STGVOL command was issued.
Backup and Recovery
AS/400 or IBM eServer iSeries; Cross-Platform; Intel PC; Netfinity or IBM
eServer xSeries; RS/6000 or IBM eServer pSeries;
OS/390 or IBM eServer zSeries
OS/400; AIX; HP-UX; Linux; Solaris; OS/2; Windows; MVS; OS/390; VM; z/OS
REPAIR STGVOL, IC37275, database, corrupt, ANR9999D, abend0C4,
AS.Volume.Status, Crash, dump, signa, sig 11,
segmentation violation, server, restarted
Sam J. Giallanza
Tivoli Certified Consultant
Field Issues Manager
Field Input Communications (FIC)
giallanz AT us.ibm DOT com
520.799.5512 - T/L 321.5512
Our new web Support site and KB is at :