Hi, Victor.  You can pre-define volumes into storage pools with the
"define volume" command.  Set those stgpools to maxscratch=0 and you
should be able to avoid having the wrong volsers used in the wrong
pools.  See the Admin Guide, Chapter 2, Concepts, for "Defined volumes
and scratch volumes" > "Preparing tape volumes with an automated library".

It's a bit more administrator overhead, but most of that can be handled
by gratuitous use of shell scripting.  Unless there are concrete
drawbacks to using the same volser range for both pools and letting them
mix, I'd avoid this approach.

Alex


On 6/28/2012 12:23 AM, Victor Shum wrote:

Dear All :



I am implementing a TSM V6 EE on AIX with IBM TS3200 with 4 x LTO5 drive.
Is it any easy way that I can use different LTO-barcode labeling scheme for
primary and copy pool ?



My concerns is : DRM will be implement to handle offsite tape cycling, when
offsite tape media back to the Tape library; it shall become "scratch" type.
So I concerns those tape may be reused by the primary pool.  So it seems
that cannot use different tape labeling scheme for primary and copy pool..



e.g. BON000 ~ BON999 label will be used for primary pool tape media;  BOF000
~ BOF999 labels will be used for all copypool..



Best regards,

Victor Shum