Same thing happened to me.   Same solution.
I.E>  when a move data to same stgpool fails then
tryed a move data to a different stgpool and it worked

disk to tape worked.

Joseph A Faracchio,  Systems Programmer, UC Berkeley
Private mail on any topic should be directed to :
   joef AT socrates.berkeley DOT edu

On Wed, 29 Aug 2001, Michel Engels wrote:

> We have the same problem. We also work on OS/390. We managed to liberate the
> disk volume doing a move data to the next storage pool. Doing it to the same
> storagepool as the disk belongs to did not work. This solved my problem so I 
> did
> not investigate more deeply.
>
> Michel Engels
> TSM Consultant
> Devoteam Belgium
>
>
>
>
>
>
> "Hunley, Ike" <Ike.Hunley AT BCBSFL DOT COM> on 08/28/2001 03:55:43 PM
>
> Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>
> To:   ADSM-L AT VM.MARIST DOT EDU
> cc:    (bcc: Michel Engels/BE/Devoteam)
>
> Subject:  Problem deleting a storage pool volumes
>
>
>
> Can someone make sense of this?  It's not making sense to me...  I'd REALLY
> appreciate some insight.
>
>
> 08/28/2001 10:48:33   ANR2017I Administrator O8X issued command: MOVE DATA
>
>                        SYS2.ADSM.STGP28 STGPOOL=BACKUPPOOL WAIT=NO
>
> 08/28/2001 10:48:35   ANR1141I Move data process ended for volume
> SYS2.ADSM.ST-
>                        GP28.
>
> 08/28/2001 10:50:27   ANR2017I Administrator O8X issued command: QUERY
> ACTLOG
>                        search=stgp28
>
> 08/28/2001 10:50:44   ANR2017I Administrator O8X issued command: DELETE
> VOLUME
>                        SYS2.ADSM.STGP28 DISCARDDATA=NO WAIT=NO
>
> 08/28/2001 10:50:50   ANR2017I Administrator O8X issued command: QUERY
> ACTLOG
>                        search=stgp28
>
> 08/28/2001 10:51:12   ANR2017I Administrator O8X issued command: MOVE DATA
>
>                        SYS2.ADSM.STGP28 STGPOOL=BACKUPPOOL WAIT=NO
>
> 08/28/2001 10:51:12   ANR2209W Volume SYS2.ADSM.STGP28 contains no data.
>
> 08/28/2001 10:51:20   ANR2017I Administrator O8X issued command: DELETE
> VOLUME
>                        SYS2.ADSM.STGP28 DISCARDDATA=NO WAIT=NO
>
> 08/28/2001 10:51:20   ANR2406E DELETE VOLUME: Volume SYS2.ADSM.STGP28 still
>
>                        contains data.
>
> 08/28/2001 10:51:25   ANR2017I Administrator O8X issued command: QUERY
> ACTLOG
>                        search=stgp28
>
> 08/28/2001 10:51:50   ANR2017I Administrator O8X issued command: MOVE DATA
>
>                        SYS2.ADSM.STGP28 STGPOOL=BACKUPPOOL WAIT=NO
>
> 08/28/2001 10:51:50   ANR2209W Volume SYS2.ADSM.STGP28 contains no data.
>
> 08/28/2001 10:51:57   ANR2017I Administrator O8X issued command: DELETE
> VOLUME
>                        SYS2.ADSM.STGP28 DISCARDDATA=NO WAIT=NO
>
> 08/28/2001 10:51:57   ANR2406E DELETE VOLUME: Volume SYS2.ADSM.STGP28 still
>
>                        contains data.
>
> 08/28/2001 10:52:04   ANR2017I Administrator O8X issued command: DELETE
> VOLUME
>                        SYS2.ADSM.STGP28 DISCARDDATA=YES WAIT=NO
>
> 08/28/2001 10:52:04   ANR2406E DELETE VOLUME: Volume SYS2.ADSM.STGP28 still
>
>                        contains data.
>
> 08/28/2001 10:52:08   ANR2017I Administrator O8X issued command: QUERY
> ACTLOG
>                        search=stgp28
>
>
>
>
>
> Blue Cross Blue Shield of Florida, Inc., and its subsidiary and
> affiliate companies are not responsible for errors or omissions in this e-mail
> message. Any personal comments made in this e-mail do not reflect the views of
> Blue Cross Blue Shield of Florida, Inc.
>