View previous topic :: View next topic |
Author |
Message |
zoobink Beginner
Joined: 01 Feb 2004 Posts: 9 Topics: 1
|
Posted: Sun Feb 01, 2004 6:07 am Post subject: DFSMShsm Primary Migration |
|
|
When I run Primary Migration, HSM always asks for ML2 tapes to be mounted. Is there a way of running Primary Migration but only allow the migration to ML1 DASD?
Sometimes there is a shortage of available 3590 drives and it would be good if we could avoid the ML2 allocation. |
|
Back to top |
|
|
warp5 Intermediate
Joined: 02 Dec 2002 Posts: 429 Topics: 18 Location: Germany
|
Posted: Mon Feb 02, 2004 1:57 am Post subject: |
|
|
Some of your management classes are probably migrating directly from disk to ML2 ! This is probably done to prevent ML1 from getting full with huge datasets. Check into it. |
|
Back to top |
|
|
zoobink Beginner
Joined: 01 Feb 2004 Posts: 9 Topics: 1
|
Posted: Mon Feb 02, 2004 2:58 am Post subject: |
|
|
Yes they are. I want to know if there is a way that I can selectively bypass these migrations.
Sorry, maybe my question wasn't exactly clear.
For instance if I want to prevent all recall processing from tape volumes but allow recall processing from DASD volumes, I can issue the
command "HOLD RECALL(TAPE)"
So what I'm after is a way of achieving the same with migration.
If auto migration is running and asks for a tape to be mounted after the drive is allocated, but one cannot, then HSM will issue. ARC0560E MIGRATION LIMITED: NO TAPE MIGRATION VOLUME AVAILABLE
Migration will then continue but only migrate to ML1 volumes.
So, what I'm after is probably a storage patch that could be issued to make HSM believe that migration is LIMITED. |
|
Back to top |
|
|
|
|