Joe;  You could do the following:

Set up your storage pools as:  DISK --> 3480 --> 3490
I think this is what you started out doing.  Make the 3480 storage pool
READONLY.  Whenever data is migrated/moved from disk, it will bypass 3480
and go right to 3490.  The data on 3480 will still be accessible, but no
new data will be written there.  Eventually, much of the data would expire
on its own, but probably not all of it.  You can then MOVE DATA a tape at
a time, to 3490, as operator resources allow.  I haven't tried this myself,
but I think it should do what you want.

Perhaps someone else has another idea?

..Paul

Paul Zarnowski                     Phone:   607/255-4757
Cornell Information Technologies   Fax:     607/255-6523
Cornell University                 US Mail: 315 CCC, Ithaca, NY 14853-2601
--
On Tue, 25 Apr 1995 16:23:41 PDT Joseph A. Faracchio said:
On Tue, 25 Apr 1995 16:23:41 PDT Joseph A. Faracchio said:
>We have been using 3480 cartridges on a VM system for over a year now
>with about 100 users (with *LOTS* more coming real soon now.)
>I've recently gotten access to 3490s and have them working with VMTAPE,
>too.
>
>So I changed the NEXTPOOL parms of the 3480s to point to the 3490s and it
>immediately started to move (what looked like) all the data to the
>the 3490s.   I quickly cancelled that PROCESS because it was not what
>I intended.   It did raise the question of what the HI & LOW parms mean
>when you're talking about tape media.  (It means nothing when you have no
>NEXTPOOL but when one exists then what??? (compared to DASD!)
>
>And, with COLLOCATION ON, will it move *all* a users data to new 3490s when
>its moving *any* of it from dasd to tape?
>
>Someone suggested making the 3480s a READ/ONLY group but then I'm confused as
>to whether to make the 3490s part of the same STGPOOL or a NEXTPOOL group?
>
>      thanks for your help!
>
>                .. joe.f.