IBM Data & AI

 Welcome to the IBM Data & AI Ideas Portal for Clients! 

We welcome and appreciate your feedback on IBM Data & AI Products to help make them even better than they are today!
Before you submit an idea, please perform a search first as a similar idea may have already been reported in the portal.  If a related idea is not yet listed, please create a new idea and include with it a description which includes expected behavior as well as why having this feature would improve the service and how it would address your use case.
IBM Employees:
  • Our team welcomes any feedback  and suggestions you have for improving our offerings / products!  This forum allows us to connect your offering / product improvement ideas with IBM product and engineering teams.
  • If you have not registered on this portal please click on the following link and register.  To complete registration you will need to open the email you will receive from Aha to confirm your identity.
Additional Information:
  • The shorter URL for this site is:
  • To view our roadmaps:
  • Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases
  • Please do not use the Ideas Portal for reporting bugs - we ask that you report bugs or issues with the product by contacting IBM support.

Summary Grouping and Detail Breakdown of Autonomics Actions by Symptom

It would be helpful if the Autonomic Console within the DB2 Automation Tool provided the ability to see both a summary grouping and a detail breakdown by symptom of any autonomic actions (either passive or active) within a maintenance window. A similar function could also be provided through the use of a symptom 'filter' on these panels.

This functionality would allow the DBA to much more easily see which objects are being flagged for the same symptom, and to take any action as deemed necessary. For example, as pending ALTERs are executed against DB2 objects, the affected objects are placed in AREO* status. Assuming this status is defined in an exception profile for REORG, this function would allow the DBA to easily identify all objects that are being flagged for reorg because they were altered by someone. The only way to do this currently is to manually look at the symptoms that were triggered for each object. This is very tedious when hundreds of objects are flagged for autonomic action each week.

  • Perry Shindle
  • Jun 17 2019
  • Will not implement
Why is it useful?
Who would benefit from this IDEA? DBAs
How should it work?

It would seem to be logical to provide this ability as a sub-function or as a command on both panel HAA$ALR3 - Autonomic Actions, and panel HAA$ALRT - Autonomic Actions. 

So, for example, from panel id “HAA$ADMX” - Autonomic Maintenance Window, you would select the maintenance window that you wanted to look at.  Then on panel HAA$ALR3 - Autonomic Actions, there would be a new primary command that would take you to a Symptom Summary panel


                The Symptom Summary panel could look something like:



  SYMPTOM SUMMARY                                                          COUNT                       


_ INDEXSPACESTATS.TOTALENTRIES                                                6  

S REALTIME_REORG_IX.NUMLEVELS_UPDATED                                         7  

_ REALTIME_REORG_IX.PSEUDO_DEL_PCT                                            3  

_ REALTIME_REORG_TS.UNCLUST_INS_PCT                                           4  

_ REALTIME_RUNSTATS.INS_UPD_DEL_PCT                                          55  

_ SYSINDEXPART.CARDF                                                        160  

_ SYSINDEXPART.LEAFDIST                                                     135  

_ SYSINDEXPART.LEAFFAR                                                       33  

_ SYSTABLEPART.CARDF                                                          5  

_ SYSTABLEPART.PERCINDREF                                                     1  

_ TABLESPACESTATS.TOTALROWS                                                  52

_ DISPLAY_AREO*                                                             3


From this panel, you could then select any listed symptom to see all of the objects that were triggered by that symptom. Using the sample panel above,

if I selected the symptom “REALTIME_REORG_IX.NUMLEVELS_UPDATED”, something similar to the following detail panel would be displayed.



     HAAxxxxx V4R2   ----------- Objects by Symptom  ----------- 2017/04/20  17:13:55

Option  ===>                                                  Scroll ===> CSR 


Line Commands:


Window Name  . . .   DB2_SUNDAY_MAINTENANCE                                  

Window Description                                                            

SSID . . . . . . . . DB2A       (Blank for any datasharing member)



                                                            Row 1 of 7        +> 


    Target           Target              Target                               

Cmd Qualifier        Object              Part   Priority    Action   Status   

         DAPRAS           XABREAS1            ALL                REORGIX  OPEN     

    DAPRAS           XABRES1             ALL                REORGIX  OPEN     

    DAPRAS           XAPPCOM1            ALL                REORGIX  OPEN     

    DAPRAS           XAPPLD1             ALL                REORGIX  OPEN     

    DAPRAS           XAPPLD2             ALL                REORGIX  OPEN     

    DAPRAS           XAPPLD3             ALL                REORGIX  OPEN     

    DAPRAS           XAPPLRE1            0001               REORGIX  OPEN        

Idea Priority Medium
Priority Justification This function would provide valuable insight into what symptoms are most frequently one of the triggering causes of a REORG (as well as which symptoms are not)
Customer Name PennDOT
Submitting Organization
Submitter Tags
  • Attach files

NOTICE TO EU RESIDENTS: per EU Data Protection Policy, if you wish to remove your personal information from the IBM ideas portal, please login to the ideas portal using your previously registered information then change your email to "anonymous@euprivacy.out" and first name to "anonymous" and last name to "anonymous". This will ensure that IBM will not send any emails to you about all idea submissions