MIM0100A

FILE nn - possible lockout info

Reason:

An I/O transaction to the primary control file has not completed in a reasonable time. A lockout may have occurred. The ID for the primary control file is shown in place of the nn variable. For a DASD control file, the unit and volume serial number of the device on which this control file resides also are shown. For a coupling facility list structure, the name of list structure is shown, along with the name of the system last known to hold the list structure lock.

This problem is caused by one of these conditions:

There is excessive activity on the volume, control unit, or channel that is associated with this control file. This is a likely cause if message MIM0100 is being issued frequently.
An external system issued a long RESERVE request for this control file.
Other systems are dominating this control file.
Hardware or software that has failed on an external system while it held a reserve for this control file.
The device on which the control file resides failed.
A channel or control unit to this control file failed.
Another job or task on this system is preventing CA MIM from being dispatched.
CA MIM on the external system that holds the DASD reserve or list structure lock is hung or looping.

CA MIM deletes this message automatically if it can complete the I/O transaction.

Action:

Wait to see if the I/O transaction completes in the next few minutes. Then take the appropriate action:

If the transaction completes, then determine whether excessive activity or RESERVE requests caused the lockout. Consider moving the control file to another location if there is excessive activity.
If the transaction does not complete, or if you have been experiencing hardware problems with one of these devices, then you need to initiate migration to an alternate control file. To do this, reply ABANDON to this message. For example, if 02 is the two-character ID that precedes this message, specify 02,ABANDON to initiate migration.

Use the MIGRATE command to initiate migration in response to this message. If you issue a MIGRATE command, CA MIM initiates migration again after this control file lockout has been resolved.