Add Support for DB2 Topology Configuration Anomalies: Single points of failure

Single points of failure within the topology as it relates to DB2 best practices. The exciting part of this is that it represents a new category of reports based on our topology reports and existing capabilities. The new type of report is a configuration exception report (similar to reports we have in SAN). I am hopeful that we can trigger a bunch of new and similar reports once people see this capability.

New Report (Single Point of Failure): Show a list of exceptions to best practice for online DB2 attachments.

Benefit: Helps the analyst understand where they have potential single points of failure across Plex, System, Data Sharing Group and Data Sharing member(subsystem)

The current topology reports serve as a basis for the information:

DB2 AUTH ID Topology

DB2 CICS Tran Topology

There will be one tabular repot with a list of links to a topology report that meets any exception to the best practice (Single points of Failure). Default should be 7 days.

From any Data Sharing Group, there will be an additional drill down report that shows Successful Prepare to Commit (Phase 1) Requests associated DB2 Data Sharing Member (DB1F and DB2F in this example):

This chart could also be expressed as a balance chart. That could be a separate drill down.

Work estimate: 10 days.

FYI: Best practice criteria:

2 CECS

4 LPARS

1 Data sharing Group

4 Members - Each member on a different LPAR

Also, only the online attachments will be considered in this: DRDA and CICS ATTACH.