Messages › CA MIM Messages › MIM0062W

MIM0062W

System sysid in file type - CRITICALLY non-responsive ##########

Reason:

The specified system has not updated its time stamp recently, and CA MIM cannot resume normal operations until it knows more about the status of this system. All global activity for CA MIM on the local system is suspended until that system responds. The current control file is identified in this message. If this control file is a virtual control file, then the value “VCF” appears in place of the type variable. If this control file is a DASD control file, then its ID appears in place of this variable.

CA MIM issues this message during migration processing to indicate that an emergency exists, or when a system is waiting or in a critical state. This message may be reissued several times.

A system can appear to be inactive for any of these reasons:

• The status of the system was changed. For example, the system was stopped.
• You did not start CA MIM on that system, but CA MIM found ID of that system in the control file.
• The system no longer exists, but its ID remains in the control file.
• (z/OS only?) Another job or user on that system is using all of the time of the processor, which prevents CA MIM from being dispatched.
• CA MIM has terminated on that system.
• A local task issued a long RESERVE request for the control file.
• A hardware or software error occurred on the system.
• The system is migrating to a new control file.

Action:

Determine why this system appears to be inactive.

If this system will not be recovered, or CA MIM will not start on the system for an extended period, or both, then issue the FREE command to free that system.

WARNING! Integrity exposures can occur when using the FREE command. For more information about possible integrity exposures when using the FREE command, see Product Termination Considerations in the chapter “Advanced Topics” in the CA MIM Programming Guide.

If you are not placing this system under the control of CA MIM, then remove the ID of that system from the control files. CA MIM retains IDs for every system on which it has executed until you specifically remove these IDs from the control file. Use the REMOVE command to do this. In addition, you should remove the systems IDs from the DEFSYS statement in the initialization member.

Otherwise, restart CA MIM as soon as possible.

For more information about freeing inactive systems and about removing IDs from control files, see the CA MIM Programming Guide.