No, this is not possible within TSM either.

You are a member of the TSM/ADSM list so don't try to register elsewhere.  I
don't think there is an elsewhere.  This is where all the really cool TSM
people hang out anyway!

I suppose an idea might be to configure the second jukebox as the nextstg
target of the first.  Any new images would be stored in the second jukebox
as the first one is full.  If not full, lower the migration threshold to
force the data to be stored in the second.

By doing this you eliminate the need to create a second management class or
policy domain to direct the data to the new pool you must create in the new
jukebox.  The existing structure will use the new storage by virtue of the
nextstg parameter.  This configuration will not effect performance.  Rather
than treating the two jukeboxes as one, you work at the storage pool
hierarchy level which offers essentially the same thing.

If I've missed something here, scream.

Thanks,

Kelly J. Lipp
Storage Solutions Specialists, Inc.
PO Box 51313
Colorado Springs, CO 80949
lipp AT storsol DOT com or kelly.lipp AT storserver DOT com
www.storsol.com or www.storserver.com
(719)531-5926
Fax: (240)539-7175