I would suggest that using the same stgpool might be a problem - if you ask
for a mount of an old tape, you could have big problems.  At a minimum, you
would need to mark all of the "filling" tapes as "read only" to prevent them
from being mounted for output - a physical impossibility in this case I
believe, but ADSM will still try.

I would suggest defining a new stgpool, (and associated devclass) and then
setting it up as the level 2 pool - update the DASD pool to migrate to this
pool.  Then, to handle migration of data from the old pool to the new pool,
set it to migrate to the new stgpool.  When you are ready to migrate the data
to the Magstar pool, simply set the high and low thresholds down, and let it
go.  If you want to stop it, simply set the limits back to 100, then cancel
the migration process.

We used this process to move from one pool to another, and it worked very
well.

Jerry Lawson
jlawson AT thehartford DOT com


______________________________ Forward Header __________________________________
Subject: Re: Device Classes
Author:  INTERNET.OWNERAD at SNADGATE
Date:    3/6/98 12:41 AM


Update stg?

Kelly