Change to 'Active DB2 Systems' panel

When viewing the DB2 Tools Launchpad and the list of tools installed, enter '?' for a list of active SSIDs.

The list that returns includes all DB2 Systems by name, but only the descriptions of the subsystems that match entries in the currently allocated SADBTLIB(ADBTPARM).

If your installation model includes a test panel mapping to test libraries (including test SADBTLIB), then you will only see the descriptions of the subsystems entered there.  Your production panel will use production libraries (including production SADBTLIB) and you will only see the descriptions of the subsystems entered THERE.   So, even though other subsystems are present, and they are selectable, the descriptions are not completely populated.

Additionally, one DB2 subsystem is listed with an incorrect GROUP.   In my environment, I have up to 8 local DB2 subsystems when I am logged on to lpar MVSA.  They are each a part of a different datasharing group.   My SADBTLIB is intended for my "special" datasharing group so SADBTLIB(ADBTPARM) contains a description for my local subsystem which is part of the datasharing group and for the datasharing group itself.  However, there is another subsystem which is listed as being part of the special datasharing group (it is not).  So of the 9 lines on this panel (8 local subsystems and the datasharing group listed in SADBTLIB(ADBTPARM)), 6 have NO group listed.  The remaining 3 all list the special datasharing group, but one of these three is simply incorrect.

For example, this display:

Sel DB2 System Description                                                Group
--- ---------- ---------------------------------------------------------- -----
    LD00                                                                      
    LD33                                                                      
    MD01                                                                      
    PD00                                                                  TG02
    PD32                                                                      
    TD01                                                                      
    TD07       DB2-TG02-SPECIAL                                           TG02
    TD32                                                                      
    TG02       DB2-TG02-SPECIAL                                           TG02

...shows TD07 and TG02 as being part of TG02, which is correct.  PD00 is part of PG01 NOT TG02 and should never be listed as a part of TG02.  Additionally, the Description field is only filled out for subsystems in the special datasharing group (TG02) ADBTPARM.