DSNB328I to be issued when all attempts to automatically recover GRECP are exhausted in all scenarios

During DR testing on several occassions the DBAs at Walmart have found that there are circumstances where neither  DSNB328I nor DSNB317I are issued and Db2 z/OS has exhausted all tries to automatically recover GRECPs. In these scenarios they were starting as many as 100 Db2 members many of which initially had GRECP objects. When starting that many members they need some reliable way to know when automatic GRECP recovery is complete and whether there are still objects in GRECP. They rely on these DSNB328I nor DSNB317I to understand the status. DSNB328I tells them there are still GRECP objects, but Db2 will no longer attempt auto recovery. DSNB317I tells them there are no more GRECP objects.  Until they get one of these msgs they wait. In scenarios where auto recovery is attempted 3 times and each time hit an ICF error, the auto recovery is ended and not retried but DSNB328I is not issued. This has meant up to 30 minutes of wasted time spent waiting for GRECPs to be recovered after Db2 had given up. Walmart have been told they can look to see if there is work running that looks like this 014.AUTOGREC or 014.DRSTRT02 to see if automatic GRECP recovery is still being attempted, but when you are in a disaster recovery scenario where there is likely chaos and where 100s of Db2 members are starting at the same time this is unrealistic and overly burdensome. Walmart needs IBM to issue either a DSNB317I or DSNB328I when Db2 stops trying to automatically recovery GRECP objects in all scenarios.  The cases Walmart opened for this is TS003012775 and TS002647405.