Quality Dashboard
The Quality Dashboard provides insight into two KPIs, Escaped Abend Ratio and the Median Time to Detect since Compile Metric.
To populate the dashboard, provide a definition of the PROD, DEV, TEST, and QA LPARs. For more information on the list of all known LPARs and a spreadsheet to fill out, contact the zAdviser team.
Quality Dashboard Metrics
This is the Escaped Abends Ratio – It represents the Number of Unique Abends that occurred in Production compared to the overall number of Unique Abends.
A unique Abend is defined by Abend Type (e.g. SOC7, S0C4, U4038,etc.) Offset, Load Module, CSECT.
An Abend that occurs 50000 times in a CICS region is considered one abend.
This is the number of Programs that have abended. If if a program had two unique abends, it is only counted once in this metric.
Total Number of Unique Abends across both PROD and DEV/TEST/QA environments.
This is the total number of abends that occurred during the selected time period. So if a CICS txn abended 50,000 times at same offset and same abend code, it is counted 50,000 times in this metric.
The Median Time to Detect since Compile is the 50 Percentile (Median value) of the number of days since the program was last compiled to the time that it abended.
For DEV environments, a user would want to see a low value here (i.e. Fail Fast) and for PROD you should want to see a higher number as that indicates that the abends may be coming from a unique set of circumstances.
The breakdown of UNIQUE Abends in PROD vs DEV.
A time series graph of unique Abends. Green is DEV/TEST and RED is PROD. The term ESCAPED Abend is an Abend that occurs in PROD and Trapped Abend is an ABEND that occurs in DEV/TEST/QA environment.
The graph can give an indication of quality. A red Sloping line going up would be indicative of decreasing quality while a sloping line downwards would be increasing quality.
Unique Abends
The LPARs where the UNIQUE Abends are occurring
Abend-AID tags the Abends Batch, IMS or CICS. This is a distribution of where the UNIQUE Abends are occurring.
This breaks the Unique Abends down by Abend Type. An Abend that begins with “S” such as a S0C4 is considered a SYSTEM abend, an Abend that begins with an “A” is considered a CICS abend and an abend that begins with a “U” is a User Abend. Any abend that does not fit into that categorization is placed in the OTHER category.
This is chart indicates the programs with the most unique ABENDs. Placing your cursor over a bar will provide the data shown in the image.
This data table provides the same information as the previous visualization. The data table can be easily exported to a Excel spreadsheet by clicking “Formatted”.
This data table adds the Abend Code and Program Type (B=Batch, C=CICS, I=IMS) to the data table. In this example, there were 5 separate offsets where a S0C7 abend occurred. The Compile data is the data the Program was last compiled before the Abend. The date format is YYYYMMDD where YYYY is Year, MM is Month and DD is Day of month.
This shows all Unique Abends with Offset where Abend Occurred and Time To Detect which is the number of days since the Program was compiled to when it first Abended.
This two visualizations provided the same Data. The first visualization is a horizontal bar chart to visually indicate the TOTAL number of abends that occurred in each Program. The second visualizations is a data table which allows for export to a CSV file by clicking on the “Formatted” button.
Abend Occurrences
This shows the total ABENDS by Abend Code.
This shows the TOTAL abends by Program, Abend Code and Program Type.
INSIDE THIS TOPIC
ZADVISER NEWS
ZADVISER SUPPORT