I always schedule Secondary Space Mgt. before Primary in order to free up space on my ML1s. Perhaps you need to reduce the ML1 days either in your SMS MGT. classes or Parmlib ML1Days parameter for non-SMS data to accelerate data movement to ML2, if your SLAs haven't taken that flexibility from you.
To answer your question: TSO HSEND SETSYS SECONDARYSPMGMTSTART(1245 1655) then after migration is done, reset to your normal time. You might consider reducing the threshold on your ML1 volumes to 50% or less, or add more ML1s. -----Original Message----- From: John Dawes [mailto:[EMAIL PROTECTED] Sent: Thursday, August 10, 2006 10:21 AM To: [email protected] Subject: Re: DFHSM QUESTION Thanks David for the tip. I found the error which was posted earlier and was not trapped: *ARC0560E MIGRATION LIMITED: NO MIGRATION LEVEL 1 SPACE 561 ARC0560E (CONT.) AVAILABLE ARC0559I SPACE MANAGEMENT OF SBP137 WILL NOT TARGET 562 ARC0559I (CONT.) MIGRATION LEVEL 1 UNTIL THE REQUESTED VOLU ARC0559I (CONT.) MADE AVAILABLE ARC0559I SPACE MANAGEMENT OF SBP133 WILL NOT TARGET 563 ARC0559I (CONT.) MIGRATION LEVEL 1 UNTIL THE REQUESTED VOLU ARC0559I (CONT.) MADE AVAILABLE ARC0400I VOLUME SBP137 IS 55% FREE, 00003628 FREE 564 The problem was resolved by itself. However, in the future should I need to MIGRATE LEVEL 1 to MIGRATE LEVEL 2 how do I do this? Is there a way to force DFHSM to perform a migrate of LEVEL 1 to LEVEL 2 out of its scheduled time? This would be necessary in case of an emergency. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
