Troubleshooting › How You Respond to Control File Access Delays › Message MIM0200W

Previous Topic: Message MIM0100A

Next Topic: How You Activate Tracing

Message MIM0200W

CA MIM issues message MIM0200W if it cannot access its virtual control file. The VCFMAXDELAY parameter on the SETOPTION command determines how many seconds CA MIM waits before issuing the MIM0200W message.

To resolve problems indicated by this message

  1. See if the master system failed. To do this, issue the DISPLAY SYSTEMS command from your master system. The ID for the master system is shown in the MIM0200W message.

    What response do you receive?

    Message IEE0305I

    CA MIM failed on the master system.

    Important! Restart it on that system as soon as possible since integrity exposures can occur while CA MIM is inactive.

    Message MIM0108I

    The master system did not fail; it is still active. Go to Step 2.

    None

    A hardware or software failure occurred on your master system. Determine whether z/OS failed or a task on your master system is preventing other tasks from being dispatched. Then, correct the error.

    If you are sure that the system will not be recovered immediately, then free resources held on that system. To do this, issue a FREE command on any other system. For example, to free resources held on system A1, issue a FREE A1 command from another system. CA MIM then initiates migration to a backup DASD control file or a new master on all other systems. You do not need to take any further action unless migration cannot complete.

  2. See if a CTC device or XCF communication failed. To do this, look at the STATUS field on the MIM0108I message displayed on the master system.

    Does the value RESERVE appear in the STATUS field for any system?

    No

    A CTC device or XCF communication failed. As a result, migration did not begin as it should have. Initiate migration to a backup DASD control file, if available, by issuing a MIGRATE command that identifies the current master system and a DASD control file. For example, to migrate from the master system SYS1 to DASD control file 03, issue a MIGRATE CF=03 command. Other systems join the migration process automatically.

    If no DASD control file is available, then initiate migration to a new master system.

    Also, you may need to reset the CTC device. To see if this is necessary, issue a DISPLAY CTCPATH from any system. If the value ERROR appears on the MIM0176 message you receive, then reset that device by issuing a CTC RESET command.

    Yes

    Note the system ID of the system for which the value RESERVE appears, and go to Step 3.

  3. See if the system that has the virtual reserve failed. To do this, issue a DISPLAY SYSTEMS command on the system for which the value RESERVE appears in the MIM0108I message.

    What response do you receive?

    Message IEE0305I

    CA MIM failed on that system while the system held a virtual reserve for the control file.

    Important! Restart it on that system as soon as possible, since integrity exposures can occur while CA MIM is inactive.

    Message MIM0118E

    An unexpected error occurred. If migration does not start automatically, then initiate migration to a backup DASD control file, if available, or migrate to a new master system. For example, to migrate from the Virtual Control File managed by system SYS1 to DASD control file 02, issue a MIGRATE CF=02 from any system. Then contact CA Technical Support.

    None

    A hardware or software failure occurred on that system while it held a virtual reserve for the control file. Determine whether z/OS failed or a task on this system is preventing other tasks from being dispatched. Then, correct the error.

    Follow this sequence to maintain system integrity:

    1. See if CA MIM is being dispatched on the inactive system. To do this, issue the following z/OS command several times from the apparently inactive system: 
         D A,MIMGR

      Note that MIMGR is the name of the CA MIM started task. See if CPU use changes.

    2. If the CPU use does not change, then CA MIM is not being dispatched. Determine which task on that system is preventing other tasks from being dispatched and correct the error.
    3. If you are sure the system will not recover immediately, then free resources held on that system by issuing a FREE command on the master system.