Moving a MIM DASD Control File
search cancel

Moving a MIM DASD Control File

book

Article ID: 49819

calendar_today

Updated On:

Products

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

Issue/Introduction

How to move a MIM DASD Control File (CF) to a different volume.

Environment

Release: all
Component: MIM

Resolution

There can be multiple reasons for wanting to move a MIM DASD CF. One reason is to improve dataset placement (isolate a MIM CF). Another reason is if you have more than 1 CF on the same volume - if the device fails, you will lose more than 1 MIM CF.

There are 2 ways to move a MIM DASD CF:

  1. If you can schedule a MIM global outage, that is an easy way to move a MIM CF. You can follow these steps:

    • Shut down MIM on all systems.
    • Delete the CF to be moved.
    • Re-allocate the CF on the new volume. You can use sample JCL provided in member ALLOCCF in the MIM.CNTL PDS.
    • If you keep the same DSN and you catalog the new CF, then you don't have to change your MIM Proc JCL or any MIM ALLOCATE command you may be using in MIMINIT for the CF.
    • Format all control files by specifying FORMAT=CF on the z/OS START command on the first system where MIM is restarted.
    • Perform a normal startup (no formatting) on subsequent systems where MIM is restarted.


  2. You can dynamically move a MIM DASD CF, without having to stop any MIM address space. You can follow these steps:

    • If the CF to be moved is the current CF, then use the MIM MIGRATE command on 1 system to migrate to an alternate CF. The MIM command D FILE will show the current status of each CF.
    • On every MIM system, issue the MIM DEALLOCATE command to free the CF:
      DEALLOCATE DDNAME=MIMTBLnn where nn can be determined from the File column in the D FILE output
    • Delete the CF to be moved.
    • Re-allocate the CF on the new volume. You can use sample JCL provided in member ALLOCCF in the MIM.CNTL PDS.
    • If you keep the same DSN and you catalog the new CF, then you don't have to change your MIM Proc JCL or any MIM ALLOCATE command you may be using in MIMINIT for the CF.
    • On every MIM system, issue the MIM ALLOCATE command to allocate the new CF:
      ALLOCATE DDNAME=MIMTBLnn,DSN=your.mim.cf.name
    • The new CF will be automatically reformatted on the first system on which it is allocated.
    • To verify that the CF is usable, you can use the MIM MIGRATE command to force a migration to the new CF.