I just went through that.  Try an AUDIT VOLUME <volname> FIX=YES.

Bjørn Harald Sandvik
Statoil

To:       ADSM-L @ VM.MARIST.EDU
cc:        (bcc: Bjørn Harald Sandvik)
From:     evanloon @ KLM.NL @ INTERNET
Date:     11.12.97 18:02:05
Subject:  Damaged volume



Content-type: text/plain; charset=us-ascii


Dear ADSM-ers,
I have a volume which is unreadable. No copy is available, so I would like
the references to the data on the volume removed form the database, so a
new backup will be taken tonight.
I though an UPDATE VOLUME ACCESSÞSTROYED would do the trick, but the
volume reference still exists.
I then issued the RESTORE VOLUME command. The response in the log was:
Restore of volumes in primary storage pool SMSPOOL started as process
65.
Restore process 65 ended for volumes in storage pool SMSPOOL.
Restore of volumes in primary storage pool SMSPOOL has ended.  Files
Restored: 0, Bytes Restored: 0, Unreadable Files: 0, Unreadable Bytes:
0.
Volume MVSADSMP.B0011358.BFS contains files that could not be
restored.
According to the  Admin Guide this should result in deleting the volume and
all file references from the database, but when I issue a Q VOL I still see
the volume listed!
What am I doing wrong?
Thanks in advance for any reply!
Kindest regards,
Eric van Loon