• May 22, 2019

Each iCluster group should have its own default database journal

In the last Tech Tuesday post we discussed the question “How do I decide between more journals and fewer journals for my iCluster configuration?” Generally it is felt that KISS (Keep it Simple Stupid) is the overriding principle, i.e. the fewer the number of journals the simpler the configuration.

In iCluster, before considering adding another journal…

As a follow-up for one last time… to more journals vs. fewer journals, if you do decide that you want another journal to help with latency, stop before you add it and consider the following.

How do I decide between more journals and fewer?

One decision that many shops face when implementing a logical replication solution is how to figure out how many journals they should be using. Many times this decision is already made for them as the application itself has defined the journaling structure. If however you get to decide, here are some pros and cons of […]

The ‘Position To’ field really does work on the iCluster monitor!

Some folks have had difficulty figuring out the purpose of the Position To field on iCluster’s WRKHASMON or WRKHATMON commands. You would think that it would allow you to position your screen so that the specified group, or journal is at the top of the display similar to PF17 after Option 12 on the WRKLIB […]

Error Handling Enhancements in iCluster 7.1 TR1

Rocket iCluster 7.1 TR1 has enhancements based around four key areas – ease of administration, replication verification, error handling and currency. In this post, the Error Handling Enhancements are highlighted.

Replication Verification Improvements in iCluster 7.1 TR1

Rocket iCluster 7.1 TR1 is now available for all customers on the Rocket Customer Portal. TR1 has enhancements based around four key areas – ease of administration, replication verification, error handling and currency. In this post, the Replication Verification Enhancements are highlighted.

iCluster 7.1 Technical Refresh 1 (TR1) is now available!

Rocket iCluster 7.1 TR1 is now available for all customers on the Rocket Customer Portal. TR1 has enhancements based around four key areas – ease of administration, replication verification, error handling and currency. In this post, the Ease of Administration Enhancements are highlighted.

Send email alerts using DMWRKALR to monitor your iCluster HA environment

In 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 have changed their status to *INACTIVE or *INDOUBT, or for specific messages in the eventlog. The next step in automation is to have EMAIL notifications […]

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.

iCuster DMSETMSTR: Set the master node explicitly

The master node in iCluster is a special concept – it is the first node created in iCluster when it is first configured and contains the master copy of the metadata. Remember it has NO bearing whatsoever on replication direction.