Automated ODD generation in CSM, along with periodic cleanup based on a retention policy to prevent storage overrun

Background:

I recently met with the Storage Infrastructure Head of a large Indian bank. During the discussion, the customer specifically asked whether DS8000 supports automatic ODD generation based on predefined thresholds or triggers at the time an issue occurs.

The question came up due to a recent MM replication issue, where an ODD dump was requested by support, but it was no longer available since time had elapsed from the actual problem occurrence. This impacted problem determination and delayed analysis. 

As per my understanding, DS8000 will take ODD in a range of situations to collect diagnostic data and it cannot cover every type of situation that clients might experience and so we provide the dscli and z/OS based interfaces to enable the user to trigger the collection. Also, software such as GDPS will trigger ODD across an entire environment including MM primary and secondary in situations where this has been seen to be useful.

Since the bank I met uses DS8000 attached to POWER-AIX environment, we would need similar capability in CSM too.

As per CSM Architect, the CSM can be used to trigger ODDs and has interfaces (CLI/REST,etc) that can be used to trigger ODDs. But, we do not automatically trigger ODDs at this time. 

Ask behind this Idea creation:

Raising an idea to automate the ODD generation in CSM, along with periodic cleanup based on a retention policy to prevent storage overrun.