Hi again,
the problem was the collocation option, it was setup
to yes.

Thanks for all


--- Richard Sims <rbs AT BU DOT EDU> wrote:
> >We have a 3575 library with 4 drives. My problem is
> >We have a 3575 library with 4 drives. My problem is
> we
> >have many volumes in filling status. I tried to do
> a
> >"move data"  from the filling tapes to disk stg
> pool
> >and after that, to do a migration to library. But I
> >found the same problem, that is, the tape pool is
> >taking scratch tapes instead of full the filling
> >tapes.
> >Somebody knows how can I solve this problem?
> >
> >The move data, in the same stg pool, don't solve
> the
> >problem, it always takes a scratch tape.
> >In addition, I haven't collocate parameter
> >configurated.
>
> Francisco - Collocation is the most common cause of
> this; but
>             you don't have it active.  This would
> suggest that you are
> suffering I/O errors on your tapes such that they go
> read-only and so
> TSM calls for a scratch each time a new action is
> performed.  This is
> easy to check with Query Volume.  And, naturally,
> have a good look at your
> Activity Log to see what's going on.
>
>    Richard Sims, BU


__________________________________________________
Do You Yahoo!?
Yahoo! Shopping - Thousands of Stores. Millions of Products.
http://shopping.yahoo.com/