I have found that I need to give the DELETE VOLHIST some time to take
effect.  I have a 30 second delay built into my script and it works
reliably.

Bob Price

Westinghouse I & T Information Systems
11 Stanwix Street
Pittsburgh, PA 15222

Email:   pricerr AT westinghouse DOT com
Voice:  (412) 642-3634, (WIN) 272-3634
FAX:      (412) 642-3929, (WIN) 272-3929


>----------
>From:  David Ong[SMTP:david AT babyong.nsc DOT com]
>Sent:  Thursday, September 19, 1996 4:40 PM
>To:    Multiple recipients of list ADSM-L
>Subject:       Backup DB & Del Volhistory
>
>Hello ADSMers,
>
>We just upgraded from AIX ADSM server v1.2.0.9 to v2.1.0.9 over the weekend.
>The
>upgrade went fine. My problem is with changing from DUMP DB to BACKUP DB to
>back
>up my database. I was dumping the db to tape daily and cycling thru 7 tapes
>for
>each day of the week via a scheduled job which invokes a simple macro. When I
>changed from DUMP to BACKUP, the command would not use the specified tape and
>would end up using a scratch tape. It turns out the BACKUP command will not
>write
>over a tape that is still logged in the database as being used for backing up
>the
>database. To get around this, I thought I could simply stick the following:
>
> DELETE VOLHISTORY TODATE=TODAY-7 TYPE=DBBACKUP
>
>into the macro and be done with it. Unfortunately, when I did that, the job
>hangs
>and I can't even get rid of the session with the cancel session command.When
>I
>reported the problem to IBM, I was told that the DELETE command was hanging
>the
>session waiting for a confirmation reply and was working as designed.
>
>If anybody out there has figured out a way to do something similar to what I
>am
>trying to do I would love to hear his/her solution.
>