• June 26, 2022

Using DMMONHA to monitor your iCluster HA environment

Using the iCluster DMMONHA command is a great way to make sure your high availability environment is performing to your expectations. You can monitor the iCluster event log for latency, suspended objects that have been suspended for more than a user specified number of minutes, and even specify up to 20 individual messages to monitor.

For groups, the same command can monitor the status of groups and let you know when the status of a group changes from Active to Inactive or Indoubt and remains in that status for more than a user specified number of minutes.

Finally you can also automatically clean up the eventlog of any expired messages (messages older than the retention period specified in the iCluster system wide value – Option 6 on the main menu).

In the example below, the eventlog is being monitored for any latency, the eventlog is being cleaned up automatically, we are monitoring for suspended objects that have been suspended for more than 30 minutes, and groups are being monitored for any groups that are in Inactive or Indoubt status for more than 5 minutes.


The use of DMMONHA will ensure that you are on top of any issues that may arise in your replication environment.

iCluster Tech Tuesday 0 Posts

iCluster TechTuesday is a set of posts covering technical tips and techniques to help get the most out of your Rocket iCluster installation.


  • Send email alerts using DMWRKALR to monitor your iCluster HA environment - Rocket Software Reply

    August 20, 2013 at 6:43 am

    […] the last Tech Tuesday post: Using DMMONHA to monitor your iCluster HA Environment we showed how DMMONHA can be used to automatically monitor for suspended objects, or groups that […]

  • Bob LeMay Reply

    August 27, 2013 at 5:47 pm

    According to the DMMONHA command help, “This parameter [“Event Message IDs to Monitor”] is used only when the value of the EVTLOG parameter [“Monitor Event Log”] is *SELECT.  So, in the example above, since “Monitor Event Log” is *SEV30, the value of *LATNCY would be ignored.

  • Mike Warkentin Reply

    August 29, 2013 at 9:37 am

    Bob LeMay  
    Good catch Bob. My BAD. You are correct. To have latency messages monitored, the EVTLOG parm needs to be set to *SELECT. Regardless of the value of EVTLOG, SEV40 messages will always be monitored but not SEV30.
    Nice to know someone is reading these posts in detail.

Leave a Comment

Your email address will not be published.