It shows a value of 15.  But what does that tell me?  Is it the actual
number of scratch volumes available or the number of potential volumes that
can be returned to scratch?

Craig

> -----Original Message-----
> From: Vraspir, Mary J. [SMTP:MJVraspir AT WEST DOT COM]
> Sent: Monday, May 17, 1999 3:12 PM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Re: Doesn't delete a volume return it to scratch?
>
> Craig,
> You should also check your maxscratch value.
> Q stg f=d
> Mary Vraspir
> West Teleservices
> Omaha, NE
>
>         -----Original Message-----
>         From:   Craig Winters [SMTP:CWinters AT OTPCO DOT COM]
>         Sent:   Monday, May 17, 1999 1:43 PM
>         To:     ADSM-L AT VM.MARIST DOT EDU
>         Subject:        Doesn't delete a volume return it to scratch?
>
>         I thought when you delete an empty volume that it goes to scratch
> area.  I
>         have done this with a couple of volumes because they were not set
> to
>         automatically to go to scratch when empty.  The reason I question
> this is
>         because when the db backup command is set to run it fails because
> it
> claims
>         there is no scratch volume available.  Does this have to do with
> any
>         retention setting?  We are running an A01 3466 with a 3575 library
> with
>         version 3.1.2.20.
>
>
>         Craig Winters, System Programmer
>         ----------------------------------------------------
>         Otter Tail Power Company
>         PO Box 496
>         Fergus Falls, MN 56538-0496
>
>         Phone: 218-739-8288
>         Fax:      218-739-8632
>         E-mail: cwinters AT otpco DOT com
>         ---------------------------------------------------
>                              =================
>           __              ___=================
>          /  \        _ __ =====
>         |    |======|_ | |  |   /\  | |
>          \__/  |  | |_ |\   |  /--\ | |_
>                            Power Company