Quick and easy is often a synonym for doomed to fail. You need to plan.
Your current setup uses tape for ML2. How much data is currently in ML2? How
long do you keep it? How rapidly does it grow?
You bought disk to replace the tape. How much disk? Is it enough to handle
all the current ML2 data plus the anticipated growth?
Do you want the data that is currently on ML2 tapes to remain in HSM or do you
want them to end up on Primary volumes?
If the datasets are to remain in HSM, you may not need to recall them
at all. Once the SETSYS ML2 units are changed, either the RECYCLE or FREEVOL
commands should move the data to DASD.
If you want the datasets on primary volumes, you will need to recall
them but you will also need to change other SETSYS options to prevent Secondary
Space Management from putting data on new ML2 volumes.
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of
George Rodriguez
Sent: Wednesday, March 16, 2011 11:55 AM
To: IBM-MAIN@bama.ua.edu
Subject: Re: How Do I Eliminate ML2 Migration?
Barry,
Are the parameter that I change these:
SETSYS
TAPEMIGRATION(ML2TAPE
(TAPE(3490)))
SETSYS
MIGUNITNAME(3490)
Does that mean that the migration still occurs, except it goes to disk? Does
it also mean that I might need to increase the migration volumes to support
migration?
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
