John,

That's pretty much the command I used, displayed in the actlog below...

Cheers,
--
Paul

John Naylor <john.naylor AT SCOTTISH-SOUTHERN.CO DOT UK> on 14/01/2003 22:29:

Paul,
You could try
del volh tod=today vol=xxxxxx type=backupset force=yes
(only the first volume in sequence is required the others will delete
automatically)

Paul Ripke <pripke AT csc.com DOT au> on 01/13/2003 06:58:04 AM

Please respond to "ADSM: Dist Stor Manager" <adsm-l AT vm.marist DOT edu>

To:   adsm-l AT vm.marist DOT edu
cc:    (bcc: John Naylor/HAV/SSE)
Subject:  Error during "delete volhistory"


Anyone know how to delete multi-volume backupsets from volhistory?
BTW, server is 4.1.3.0 (waiting on my spare time for an upgrade...)

tsm: BHPS>q volhist ty=backupset

       Date/Time: 09/19/02   12:34:34
     Volume Type: BACKUPSET
   Backup Series:
Backup Operation:
      Volume Seq: 1
    Device Class: 3590
     Volume Name: SP0064
 Volume Location:
         Command: generate backupset ISDWOL-ES2 es2-fdrive \\isdwol-es2\f$
devcla=3590 scrat=y retent=90

       Date/Time: 09/19/02   12:34:34
...
       Date/Time: 09/19/02   12:34:34
     Volume Type: BACKUPSET
   Backup Series:
Backup Operation:
      Volume Seq: 9
    Device Class: 3590
     Volume Name: SP0469
 Volume Location:
         Command:

Actlog output looks ominous:
ANR2017I Administrator WERIPP issued command: DELETE VOLHISTORY
typ=backupset volu=SP0064 force=yes todate=today
ANR9999D tb.c(2029): Invalid Encoded Key Length
ANR0106E imarqry.c(3069): Unexpected error 100 fetching row in table
"Archive.Descriptions".
ANR9999D icvolhst.c(3473): Volume SP0064 initially found no longer exists
during volume deletion.
ANR2468E DELETE VOLHISTORY: An internal server error was encountered while
deleting server sequential volume history information.
ANR2017I Administrator WERIPP issued command: ROLLBACK

Tried first and last tape of the series, with same results.
A comma-separated list generated a "no such volume" type error.

Cheers,
--
Paul Ripke