Allow user to adjust the number of "keep alive" requests that can be missed before a storage device sends 2020 error event

IBM needs to add a feature that would allow people who manage IBM storage devices to adjust the number of "keep alive" requests that can be missed before a storage device sends 2020 error event emails about Remote Copy links being down --- 99% of the 2020 error event emails we get about replication links being down only occur when there is a very small amount of time 2 systems stop communicating, and the link status returns to normal without anything needing to be done

This feature would be helpful to companies that manage a lot of storage devices that have replication links setup like ours (data hosting company), since 99% of the 2020 error event emails we get about replication links being down only occur when there is a very small amount of time 2 systems stop communicating, and the link is back up and working by the time someone logs in to the device to make sure the link is back up.

If the link status returns to normal without anything needing to be done 99% of the time, and we have no way to stop the random times that there is a very small amount of time systems stop communicating (couple pings lost), then there are no problems a majority of the time when these emails are triggered (the link fixes itself), but we still have to take time to make sure the link is back up since we received an alert about it going down.

If IBM decided to add a feature that would send another email when the link that reported down comes back up, that would just double the number of emails we receive (since we would still get alerts about the keep alive alert being lost, and then another when it comes back). We already get too many emails about these events, so adding a feature that allows us to adjust the number of keep alive alerts lost for a remote copy partnership seems to be the best resolution to this problem (we only want emails about the link being down when we are sure the link is down).

Can IBM look in to adding a feature that would allow people who manage the device to change/set the number of "keep alive" requests that can be missed for each partnership before the device triggers this 2020 error event and sends an email?