I'm a little behind on the newsgroup, but scanning ahead slightly I haven't seen
any more references to this problem.

If this hasn't been resolved yet, I would recommend doing a database audit. (Use
FIX=NO the first time through to find out what it's going to do to you!) If
errors show up, contact ADSM support to find out how you should proceed. If
there are errors, and you don't have software support with ADSM, then you can
try the FIX=YES, or restore from a previous version of the DB backup before this
error started.





From: Eric van Loon <evanloon AT KLM DOT NL> on 06/16/98 02:22 PM GMT

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

To:   ADSM-L AT VM.MARIST DOT EDU
cc:    (bcc: ADSM)
Subject:  Re: Occupancy went negative




Hi Christopher!
What is the result from a DELETE VOLUME 208 DISCARDDATA=YES?
Kindest regards,
Eric van Loon