|
|
|
CA MIM provides a continuous health check state directly to CA OPS/MVS. CA OPS/MVS can use this information in several ways to determine the operational health of the CA MIM address space.
CA MIM issues a heartbeat update every sixty seconds that notifies CA OPS/MVS of the current operational health state of the CA MIM address space. If CA MIM detects a health state change, it immediately generates a heart beat update without waiting for the sixty second heart beat interval to expire. In this way, CA MIM provides CA OPS/MVS with a constant operational health state view of the CA MIM address space.
CA OPS/MVS can also react to the lack of a heart beat update from the CA MIM address space and an indication that there is either a potential problem with the CA MIM address space, or there is a larger system level problem that is taking place.
Note: For more information on using the CA OPS/MVS Health Check application, see the CA OPS/MVS documentation.
The CA MIM product health check heart beat state is presented to CA OPS/MVS and can be processed by the following rule:
)API CAHEARTBT
The available OPS/REXX variables for CA MIM state management are:
OPS/REXX Variable Value
API.APPLICATION MiMgr
API.VERSION Current release
API.LEVEL Service level
API.EVENTID CAHEARTBT
API.MSGID CAHEARTBT
API.TEXT Health check message text
The API.TEXT variable has the following format:
appl_id Status: health_state Reason: reason_text
Specifies the value of the API.APPLICATION variable.
health_state can be one of the following:
CA MIM is operating normally, without any detected problems.
CA MIM is operating, but has detected a potential problem that might impact normal processing.
CA MIM is operating, but has detected a problem that is impacting the processing of global resource activity.
reason_text can be one of the following:
CA MIM is operating normally, without any detected problems.
CA MIM is in the process of joining a synchronized MIMPLEX with other instances of CA MIM operating on external systems. CA MIM should only appear in this state a minimal amount of time.
CA MIM has detected a control file lock out condition. CA MIM cannot process any global resource activity on the local system.
CA MIM has detected a migration is in progress to an alternate control file of VCF MASTER system. CA MIM should only appear in this state a minimal amount of time CA MIM cannot process any global resource activity on the local system until the control file migration successfully completes.
CA MIM is in the process of performing initialization processing, in preparation to attempt to join a synchronized MIMPLEX.
CA MIM has completed initialization processing and is now waiting to begin the synchronization process with external MIMPLEX systems. CA MIM should only appear in this state a minimal amount of time.
CA MIM is in the process of quiescing in response to a CA MIM QUIESCE command.
CA MIM has quiesced processing and is now dormant in response to a CA MIM QUIESCE command. CA MIM remains in this state until it receives a CA MIM RESTART command.
CA MIM is in the process of shutting down.
The reason for the health state cannot be determined.
Members APIHRTB1, APIHRTB2, and APIHRTB3 of HLQ.OPS.SAMPLE.RULES demonstrate how you use the CAHEARTBT API.
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |