MIM auto migrate CF order usage question
search cancel

MIM auto migrate CF order usage question

book

Article ID: 430872

calendar_today

Updated On:

Products

MIM Resource Sharing (MIM) MIM Data Sharing (MII) MIM Message Sharing (MIC) MIM Tape Sharing (MIA)

Issue/Introduction

In case it will be necessary to add redundant DASD control files as a third and fourth options like so:
File 00 - XES - Coupling facility 1
File 01 - XES - Coupling facility 2
File 02 - DSN1 VOL1
File 03 - DSN2 VOL2

Questions:

  1.  If a system loses access to Coupling facility 1, are the Control Files attempted in the numerical order?
  2.  If a system migrates to another CF because a Coupling facility has been lost, would the other systems follow it in migrating to that CF automatically or a manual migrate command is needed for that to be done?
  3. In the MIM guidelines reported here:

DASD Control File Placement

 it is specified 

"Do select a device that has been excluded from synchronous or asynchronous I/O mirroring."

but if all  DASD vols are metro mirror to a global mirror source, is this considered as a major problem or just a minor performance impact?

Resolution

  1. About the CF usage order , MIM uses the next highest file number to determine which file to automatically migrate to. So, if file 01 is in use and has an error, MIM will choose file 02 next (as long as it is not marked in ERROR.)  If file 03 is in use and has an error, it will examine file 00 and select it as along as its not marked in ERROR).
  2. Assuming the 2 list structures are on different CFs, it should be very rare for MIM to ever use the DASD backup files .
  3. About the mirroring question, MIM will function normally on DASD even if its being mirrored synchronously or asynchronously. First, there is no technical reason to mirror the MIM DASD control file as there is no relevant historical data in the file to be reused. MIM handles this automatically during migration/global copy processing. Second, if the control file is mirrored synchronously, MIM does not get posted until the secondary mirrored I/O is complete . This could have a performance impact on GDIF global enq processing as control file response time may increase. If GDIF is not being used, then it is unlikely that there would be any noticeable performance impact, even with synchronous mirroring.