I know this is uncommon, but I prefer, even with LTO, to have one logical 
library per device type (LTO generation). Unfortunately, TSM doesn't understand 
many of the great features that ACSLS provides, including scratch pools. But 
with separate logical libraries, you can at least check your tapes in a type 
specific logical lib.

To really get the most out of ACSLS, you might want to take a look at Gresham 
EDT. It does provide a decent interface to ACSLS. I know a lot of EDT sites 
stopped using it because the software is not worth the money (compared to the 
native TSM ACSLS support), but Gresham may have adjusted the pricing since....

On 22 feb 2010, at 23:33, Steve Harris wrote:

> Hello List
> 
> I'm using ACSLS libraries for the first time, in a couple of sites with
> multiple TSM servers, multiple libraries. Some libraries are shared with
> TSM library sharing, and some are not. We are having issues because we
> can't use scratch tapes and must explicitly assign volumes to storage pools
> and specify volume names on db backups and backupsets.
> 
> My predecessors set this up and I'm told that things are this way because
> TSM under ACSLS can't tell the difference between the various generations
> of LTO tapes and will mount the wrong tape generation. There are also
> issues where two TSM servers share a library without a library manager
> about getting scratch tapes recognized by the right server. 
> 
> Is there any good documentation on ACSLS best practices with TSM?  How does
> the ACSLS 'owner' concept fit into partitioning libraries?  What about
> ACSLS scratch pools?  Do drives have to be dedicated to one TSM Server if
> we choose not to have a library manager?
> 
> All responses gratefully received including RTFM, provided you can point me
> at the relevant manual :)
> 
> Thanks
> 
> Steve
> 
> Steven Harris
> TSM Admin, 
> Paraparaumu, New Zealand

-- 

Met vriendelijke groeten/Kind regards,

Remco Post