Rocket Software has released a new Interim Fix package for the current release of Rocket iCluster 7.1 TR1 called Interim Fix 5 (or IF5). Interim Fix packages are less intrusive then Technical Refreshes and can usually be applied in a few minutes by extracting the IBM i save file, transferring the file in Binary mode […]
In the last Tech Tuesday post we covered how to use the DMDSPLOG command to display only the latency messages. As you are now aware, the iCluster event log contains a lot of information about your replication environment, but there may be times when you want this information in a different format or even in […]
In iCluster 7.1 TR1 we introduced CAR (Communications AutoRecovery). This feature detects small bumps in communications and automatically recovers the replications groups, including starting nodes and restarting groups from their last replication position. This is very handy if you have frequent TCP/IP errors or outages. Most of the time this is exactly what you want, […]
Back in iCluster 7.1 TR1 IF3 we introduced support for replicating SQL Stored procedures and functions. What some customers may not know is that this also works for External Stored procedures that do not use SQL. According to the IBM Knowledge Centre, an external procedure is a procedure program or service program written in a […]
If you have an application that absolutely requires that a particular object exist on the backup node but the contents are unimportant, iCluster has a solution.
The Rocket support team does an excellent job of resolving your issues and providing how to information, but they can’t read your mind. There is a certain amount of information that you should always provide to the support team to help them help you.
In iCluster 7.1 we introduced a new feature called the Access Path Rebuild Controller. Yes I admit it wasn’t the sexiest name for a new feature but PowerHA was already taken!
It’s time for a history lesson. If you look at either the Primary or Backup monitors you will see Option 12 = History. What exactly is behind that option? In a previous post, we discussed the CHGHASMON command which starts or changes the collection process for the Primary History monitor.
Did you know that since Rocket Software acquired the iCluster business from IBM in January of 2012, that the iCluster product has gone through 2 major releases (Rocket iCluster 7.1 and Rocket iCluster 7.1 TR1) with a third major release scheduled for Q4 of this year?
If you are having communications issues, you can see some of the internal comms messages that are generated by iCluster behind the scenes to assist in problem resolution.