New Alert for Active Log Dataset Time Span reaching defined Timeframe

There is lots of good instrumentation and documented processes known and available on how to calculate and monitor db2 active and archive log metrics like volumes, log switches and usage thresholds.

But each and every customer has to buid their own instrumentation on taking care of their recovery goals, especially the amount of time that is to be kept on active log dataset. Let's define this as the "active log time span", which means the timeframe covered by all currently defined active logs, from the oldest written up to the current one.

What we would like to see being added to the db2 engine, is a very basic notification (e.g. via new message in MSTR), that is issued just in case all defined db2 active log datasets have been run through or will soon start to wrapp around within a given timeframe (e.g. 24 hours).
That would show that the active log time span is falling behind the recovery goals.

This given value for this timeframe should be based on IBM best practice recommendations or even defined by a new zPARM for example.

In addition, -DISPLAY LOG command should also be enhanced to show the current time span for the currently used active log datasets.
E.g.
current active log time span = 26:45 hours (goal: 24:00 Hours)
or
current active log time span = 12:36 hours (goal: 24:00 Hours)***

These enhancements would allow customers to be alerted by db2 itself, if they run out of their recovery goals, and can set up automation on this alert. In addition, customers can easily keep track of their current active log time span.