how to cancel space reclamation if upd to unavail and reado doesn't

And, how do I kill this thing if cancelling the process, updating the
requested input volume to unavail, and updating the output volume to reado
don't kill it??


tia

lisa
----- Forwarded by Lisa Cabanas/SC/MODOT on 05/21/2003 07:30 AM -----

Lisa Cabanas/SC/MODOT wrote on 05/21/2003 07:36:21 AM:

> I am wondering if I missed something in the upgrade to 5.1, but is
> there somewhere else other than the devclass definition where I
> would define the mountwait?
>
> I ask because 140340 seconds is a lot more than 5 minutes!
>
> thanks
> lisa
>
>  Process Process Description  Status
>   Number
> -------- --------------------
> -------------------------------------------------
>       13 Space Reclamation    Offsite Volume(s) (storage pool
BACKUPCOPY),
>                                Moved Files: 117371, Moved Bytes:
>                                101,969,883,939, Unreadable Files:
0,Unreadable
>                                Bytes: 0. Current Physical File (bytes):
>                                606,188~Waiting for mount of input
> volume 771191
>                                (140340 seconds).~Current output volume:
>                                831191.\
>
>              Device Class Name: 3590TAPE
>         Device Access Strategy: Sequential
>             Storage Pool Count: 4
>                    Device Type: 3590
>                         Format: DRIVE
>          Est/Max Capacity (MB):
>                    Mount Limit: DRIVES
>               Mount Wait (min): 5
>          Mount Retention (min): 0
>                   Label Prefix: ADSM
>                        Library: MODOT3494B
>                      Directory:
>                    Server Name:
>                   Retry Period:
>                 Retry Interval:
>                         Shared:
> Last Update by (administrator): CABANL
how to cancel space reclamation if upd to unavail and reado doesn't work
