Provide more detailed information on wait times incurred when using the HA and/or DR features of the MQ Appliance

Today there is no way to tell whether network latency or other delays on the HA and/or DR interfaces are impacting the performance of queue managers making use of either or both of these features on the MQ Appliance. Excessive delays when using either or both of these features can only be inferred by using tools such as DPMON and looking at DISKBUSY time. But if DISKBUSY time is high, there is no way to tell if the busy-ness is due to writes to the local SSDs, the HA replication (if in use) and/or the DR replication (if in use). If excessive delays are seen it requires much effort to determine exactly which disk writes (local, HA or DR) are seeing the most delay. This is particularly important when DR replication is in use, since by definition this replication will be performed over a non-trivial network and distance. Being able to determine what is contributing to high DISKBUSY times in the MQ Appliance will allow slowdowns in MQ throughput due to external causes to be identified and resolved more quickly. And ideally, this information will be reported via the $SYS system topics, so we will not have to depend on service tools like DPMON to monitor this. This is especially useful when a high percentage of the traffic is NOT Persistent and might not be reflected in Log write times. Also would be very useful for predictive capacity planning.