Hi,
you can try to update libvolume 659ACP to set status to private. Then your
TSM server will not try to mount this volume as scratch.
Or you can delete this volume and define it again.

Ing. Jozef Zatko
Login a.s.
Dlha 2, Stupava
tel.: (421) (2) 60252618



                    Karel Bos
                    <Karel.Bos@NU        To:     ADSM-L AT VM.MARIST DOT EDU
                    ON.COM>              cc:
                    Sent by:             Subject:     Re: Volume is both 
scratch *and* defined in storagepool
                    "ADSM: Dist
                    Stor Manager"
                    <ADSM-L AT VM DOT MA
                    RIST.EDU>


                    22.04.2003
                    15:19
                    Please
                    respond to
                    "ADSM: Dist
                    Stor Manager"






Hi,

If you have the Scratch Volume set to no, the volume will be part of the
defined storage pool even if it is empty. It will not return to the scratch
pool.

tsm: SERVER1>q vol 659acp f=d

                   Volume Name: 659ACP
        Pct. Reclaimable Space: 0.0
               Scratch Volume?: No
Last Update by (administrator): JOSKAM
         Last Update Date/Time: 04/03/03   11:12:48

However, I don't think that is the reason of the drive errors. I would do
an
audit vol fix=yes (should be fast because the volume is empty), delete
volume and check out the volume. Have a manual look at it to see if its not
write protected. Check it in with stat=scr.

Gr.

Karel





-----Oorspronkelijk bericht-----
Van: Jurjen Oskam [mailto:jurjen AT QUADPRO.STUPENDOUS DOT ORG]
Verzonden: dinsdag 22 april 2003 15:03
Aan: ADSM-L AT VM.MARIST DOT EDU
Onderwerp: Re: Volume is both scratch *and* defined in storagepool


On Tue, Apr 22, 2003 at 07:41:16AM -0400, Richard Sims wrote:

> >...ANR8779E Unable to open drive /dev/rmt2, error number=46.
> Did you pursue the drive problem?  The AIX errno is saying that
> the drive is not ready.

All three drives work fine and don't report any errors, *except*
when TSM tries to mount 'scratch tape' 659ACP in a drive. When that
happens (doesn't matter in which drive TSM wants to mount 659ACP),
the above error is reported. Other (working) scratch tapes work fine,
in all drives.

This leads me to the conclusion that there is a problem with 659ACP,
and not a drive.

When investigating the suspected problem with 659ACP, I found the
"659ACP is both a scratch tape and defined in storage pool"-thingy. Since
there weren't any other errors logged (I/O errors in particular), I
concluded that 659ACP doesn't have a physical problem.

--
Jurjen Oskam

PGP Key available at http://www.stupendous.org/