I've been running Delete Filespace almost nonstop on our ADSM MVS server
for the past month (in the middle of an ADSM MVS to AIX migration) and
haven't run into this problem.  We're running ADSM V2.1.07 on our MVS
system.

Tim Pittson
tpittson AT himail.hcc DOT com

>----------
>From:  Eric van Loon[SMTP:evanloon AT KLM DOT NL]
>Sent:  Wednesday, August 21, 1996 10:43 AM
>To:    Multiple recipients of list ADSM-L
>Subject:       Delete filespace
>
>Hi ADSM-ers,
>
>I have done a DELETE FILESPACE for one of our nodes to purge all the
>backed up date. This however causes ALL volumes to be allocated and
>then deleted!!
>Why does ADSM allocate the volumes???? It should just update it's
>databases so the data isn't referenced anymore and then deleted during
>an normal client file space expiration process.
>We use collocation so all volumes include data from just one client.
>Which all expires at once so no allocation should be necessary. Even if
>collocation is off a allocation shouldn't be necessary because just the
>reference to the actual data (in the ADSM server databases) is removed.
>This way numerous unwanted volume mounts occur!
>Can somebody explain this?
>Thanks in advance!
>Kind regards,
>Eric van Loon
>