Primary space management causes data to be migrated to ML1 or ML2 depending on:
Management Class attributes for SMS datasets
SETSYS options (such as MIGRATIONLEVEL1DAYS) for non-SMS datasets
Secondary space management only manages datasets already moved to ML1.
What is your real goal? Are you trying to free up tapes or are you trying to
keep datasets on primary disks?
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of
George Rodriguez
Sent: Wednesday, March 16, 2011 5:28 AM
To: IBM-MAIN@bama.ua.edu
Subject: Re: How Do I Eliminate ML2 Migration?
Mike,
I just found the parm. Here's what I have:
DEFINE
SECONDARYSPMGMTCYCLE
(NNNNNNY
CYCLESTARTDATE
(1999/08/02))
But I also have:
DEFINE
PRIMARYSPMGMTCYCLE
(YYYYYYY
CYCLESTARTDATE(1999/08/02))
Does the primary space management cycle also cause a dataset to go back to
ML2 after I've recalled the dataset?
----------------------------------------------------------------------
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
