Being away from VTS for a little I do remember that the virtual volume selection
will continue in seq.
   The volumes, even though return to scratch category by the LibMgmr.   If you
defined  say 500 scratches
   to the VTS and you tested and used 100.   He is still below the scratch %
needed before he considers
   himself needing to loop back and reuse volumes.

   Somewhere in the VTS manuals it explains why in the beginning to define a
minimal of volumes to the
   VTS and why this will effect reclamation within the VTS,

   Hopes this helps a little.





Phil Hosking <phil AT AE.IBM DOT COM> on 02/29/2000 08:20:48 AM

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

To:   ADSM-L AT VM.MARIST DOT EDU
cc:    (bcc: Angelo DeAngelis/Tivoli Systems)
Subject:  ADSM + VTS



I have been implementing TSM for AIX with a 3494 VTS recently.  We have
just finished testing at the first site so decided to delete all the data
from TSM and start afresh when we went live next week.  After the deletion
it all looks fine in TSM.  We had around 4,000 virtual volumes in use and
they have all now been returned to scratch.  So we can see them with q
libvol but not with q vol.  This is as I would have expected.  On the VTS
side I am having problems fully understanding what is happening.  There has
basically been no effect on the tape utilization there.  Thus I have to
assume that while TSM has returned the VVs to scratch category and thus
deleted all pointers to the data on those VVs, the VTS does not accordingly
update it's DB to say the VVs are now empty.  If it did this I would expect
it to recalculate the utilization of the VTS physical volumes which ought
to trigger a big reclamation.

Is this behaviour correct or am I missing something?

Cheers, Phil

Phil Hosking
RS/6000 Systems Specialist
United Computer & Management Consultancy
P.O. Box 9226, Dubai, U.A.E
Tel:  009714 -3021502(direct); 00971-50-6506941(mobile)
Fax: 009714 - 3313312.
Email: phil AT ae.ibm DOT com