s" on 10/10/2000 09:45:35 AM
Please respond to "[EMAIL PROTECTED]/P=Internet/A= /C=us" @ X400
To: "[EMAIL PROTECTED]/P=Internet/A= /C=us"@X400
cc:
Subject: Re: TSM Using Scratch instead of Filling Tapes
William:
Try a:
q vol acc=reado
q vol acc=unavailable
and see if yo
Do you have colocation on your primary storage pool?
>>> [EMAIL PROTECTED] 10/10/00 09:42AM >>>
William:
Try a:
q vol acc=reado
q vol acc=unavailable
and see if your filling tapes show up.
Quoting William Boyer <[EMAIL PROTECTED]>:
> AIX 4.3.1, TSM 3.7.3.0, IBM3494, (2) IBM3590B1A
>
> Rig
That is the way adsm works if your storage pool is collocated. The order
of search for a tape is first a tape that already contains data for the
node, and next an empty scratch tape. To force adsm to put more than one
node on a tape you need to restrict the number of tapes available to the
stora
, October 10, 2000 8:32 AM
To: [EMAIL PROTECTED]
Subject: TSM Using Scratch instead of Filling Tapes
AIX 4.3.1, TSM 3.7.3.0, IBM3494, (2) IBM3590B1A
Right now I have 50 tapes in my onsite tape pool and 22 of them are in a
'Filling' state. It seems that TSM is more often selecting a scra
>Why isn't TSM calling for 'Filling' tapes instead of scratch?!?!?!?!?!?!
The most common reason is your collocation definitions.
You can use Query Content to see what node is using the scratches
vs. the Filling tapes.
Richard Sims, BU
William:
Try a:
q vol acc=reado
q vol acc=unavailable
and see if your filling tapes show up.
Quoting William Boyer <[EMAIL PROTECTED]>:
> AIX 4.3.1, TSM 3.7.3.0, IBM3494, (2) IBM3590B1A
>
> Right now I have 50 tapes in my onsite tape pool and 22 of them are in
> a
> 'Filling' state. It see
AIX 4.3.1, TSM 3.7.3.0, IBM3494, (2) IBM3590B1A
Right now I have 50 tapes in my onsite tape pool and 22 of them are in a
'Filling' state. It seems that TSM is more often selecting a scratch tape
instead of a 'Filling' tape. These 'Filling' tapes aren't reclaimed, and I
was trying to consolidate b
