Messages › CA MIM Messages › MIM0061W

MIM0061W

SYSTEM sysid IN FILE type - POSSIBLY INOPERATIVE
SYSTEM sysid IN FILE type - INOPERATIVE AT STARTUP
SYSTEM sysid IN FILE type - INOPERATIVE DUE TO SHUTDOWN

Reason:

The specified system has not updated its time stamp recently, which means that the system may be inactive. The current control file is identified. 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.

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

POSSIBLY INOPERATIVE

Indicates that an active system is not accessing the control file for unknown reasons.

INOPERATIVE AT STARTUP

Indicates that a system has not yet been started during the startup process.

INOPERATIVE DUE TO SHUTDOWN

Indicates that a system terminated due to the SHUTDOWN command.

Note: CA MIM cannot always know when a system has abended or has been shutdown intentionally, especially when the terminating system is the master system. Therefore, the POSSIBLY INOPERATIVE message may be issued about a system that has abended or been shutdown.

By default, CA MIM issues this message 30 seconds after its first unsuccessful attempt to contact that system. You can use the MARGIN parameter on the SETOPTION command to determine how long CA MIM waits before issuing this message. If CA MIM cannot contact this system soon, then it issues message MIM0063 to notify you that it considers that system to be asleep and purges its control file records for that system.

Action:

Take one of the following actions:

• 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 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. You should also remove the system IDs from the DEFSYS statement in the initialization member.
• If neither of the above actions is applicable, then restart CA MIM as soon as possible.

Note: For more information on determining whether a system is inactive and for responding to this message, see the CA MIM for z/OS Programming Guide.

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