I would be so sure.  I upgraded to the new v3.1.2.1 as instructed by IBM
support and still have the problem.  I am calling them back now to have them
explain a work around.

Anthony Jones
ADSM Administration
Koch Industries, Inc.
316-828-2432

> -----Original Message-----
> From: Robinson, Cris [SMTP:Cris.Robinson AT LIBERTYMUTUAL DOT COM]
> Sent: Tuesday, January 12, 1999 8:00 AM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Re: del volh bug?
>
> I had (Have) a similar problem on my V2 NT servers. To solve this I
> resorted
> to the following command:
> DELETE VOLHISTORY TODATE=TODAY-2 TOTIME=-48 TYPE=DBBACKUP
>
> I had to make the TODATE and TOTIME equal. strange, but it was the only
> thing that worked. Hopefully
> I won't have the problem when I go to Version 3 in a couple of weeks.
>
>
> __________________________________________________
> Cris Robinson
> Sr. Technical Analyst
> Enterprise Storage Management / ADSM
> Liberty Mutual Insurance
> Portsmouth, New Hampshire
> 603.431.8400.54837
> mailto:cris.robinson AT libertymutual DOT com
>
>
> If you find yourself in a hole, stop digging!
>
> > -----Original Message-----
> > From: Bob Booth - CSO [SMTP:booth AT CHIANTI.CSO.UIUC DOT EDU]
> > Sent: Monday, January 11, 1999 7:46 PM
> > To:   ADSM-L AT VM.MARIST DOT EDU
> > Subject:      del volh bug?
> >
> > I have just upgraded my AIX ADSM server to 3.1.2.1 and now I can't
> delete
> > my
> > database backup volume history.
> >
> > On Mondays, I issue the following command to perform a fresh backup
> > sequence:
> >
> > delete volh type=dbb todate=today
> >
> > The server now returns:
> >
> > ANR2467I DELETE VOLHISTORY: 0 sequential volume history entries were
> > successfully deleted.
> >
> > and my dbb volume history remains.  I have tried various forms of
> deleting
> > the volume history (after taking a volh backup of course), like
> >
> > delete volh type=all todate=today
> >
> > This erased everything but the dbb volume history...
> >
> > What gives?  Anyone know?
> >
> > Bob Booth