Identifying the clock differential and network latency between replication queue manager hosts

It is important to check the network latency if you are concerned about replication performance. There should not be a clock differential between replication queue managers if NTP is working properly. If NTP is not working properly, you must account for the clock differential to determine the correct latency value.

Procedure

To get clock differential and latency information:

Issue the rqmstatus command:
```
rqmstatus
```
Check the output for the following sections:
Nodes
Displays information about whether a node is local or remote. An example follows:
```
rqm1 = rqm1.example.com (local)
rqm3 = rqm3.example.com (remote)
```
Time offsets
Reports clock differential and network latency. The value (local) indicates that clock differential and network latency do not apply to the local node. The actual values indicate the differential and latency between local and remote nodes. An example follows:
```
   Node    |  Clock differential  | Network latency (ms)
-----------+----------------------+----------------------
   rqm1    |  (local)             |  (local)
   rqm3    |  00:00:01            |  0
```