You would expect that no one could restore a file from this volume,
if there really are any backup versions still on it, right?  I suggest
putting the volume to sleep and ripping the storage out from underneath
it to use for other things as you intended.  To do this --

1. update it and mark it read only or even unavailable.
2. does the vm server have a vary command? (the mvs server does).
if so, vary it offline.  At this point the vm file should be unallocated.
3. Take a vm utility backup of the file.
4. destroy the file.
5. Restart adsm, it should start without trying to get at the file.
6. Use the space for other purposes.
7. Persue the anr9999d with IBM support, as the messages & codes manual says
you should.  Eventually they may discover a bug or tell you how to repair the
db without a full dump & load.

(I am seeing more reports of anr9999d messages on the list.  Is it just
that there are more subscribers or is there something rotten in the
server code?  And when will it be my turn?)

--
--------------------------
--------------------------
Bill Colwell
Bill Colwell
C. S. Draper Lab
Cambridge, Ma.
bcolwell AT draper DOT com
--------------------------
In <0055600010531932000002L022*@MHS>, on 04/14/99
In <0055600010531932000002L022*@MHS>, on 04/14/99
   at 11:00 AM, "Moir,Betsy" <betsy.moir AT ABBOTT DOT COM> said:

>Environment:  ADSM server V2.1.0 on VM

>We need to take back a couple of volumes of DASD from one of our ADSM
>server stgpools.  The following is the process we followed:

>1.  Move Data 0511
>2.  Delete Volume 0511

>We got the error message "Volume still contains data".  We then did:

>1.  Audit volume 0511 discarddata=yes
>2.  Delete volume 0511

>We got the error message "Volume still contains data" AND one of the
>ever-popular ANR9999D messages which said:  DFQRY(449) Missing row for
>bitfile 0.29693264.

>We tried a few more times to move the data, audit the volume and discard
>the data, delete the volume, etc. and every time we got the missing row for
>bitfile 0.29693264 message.

>Has anybody ever seen this before?  Does anyone know what the "missing
>row....." message means?  Does anybody have any suggestions as to how we
>can get some of the these stgpool volumes back?  It's beginning to feel
>like some kind of science fiction movie where the machine desperately tries
>to hold onto it's life source while we are trying to rip it away.  Help -
>so far the machine is winning.