For the current ML1 data, you can issue the commands directly (hsend migrate dsn(x) ML2). There is a variation of the HSM LIST command that will show only the datasets on ML1.
You will still need (at least) 1 ML1 volume if you are using the AUTODUMP feature. This is where HSM stores the VTOC copies used in volume recovery. For the data on Primary, I would set ML1 days equal to ML2 days in the Management Class definition.. HTH, <snip> What I want to have happen All migrations go directly to tape, no longer go to ML1 DASD. But I still have a lot of migrated data on ML1 I need to get to ML2. For that I suppose I can wait for it to roll off to ML2. I changed the TAPEMIGRATION( DIRECT) thinking that anything that migrated from this point forward would go to ML2 and not ML1. But, nope, issued an HMIG command against a dataset and it went to ML1. </snip> ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
