ADI provides the detailed CICS® transaction
analysis within a service class.
Complete the following steps to view the response time, CPU time
or execution count analysis of CICS transaction. Before you begin
this activity, you need to add at least one collection with associated OMEGAMON® for CICS data provider.
- Click the IBM ADI header to go to the Workbooks view. By
default, you are on the Workbooks view after you log in ADI.
- Select the name of workbook that you want to view analysis information.
- On the summary view of that workbook, if you are not
yet on the Performance tab, select Performance tab.
- View the reports on the Performance tab. The
latest analysis information such as number of average transactions,
average CPU time, and average response time are displayed.
- Go to the Transaction Analysis view by using one of the
following steps.
- Select the transaction name that you want to view the transaction
analysis information from either Top Average Execution Count report
or Transaction Exceeding Response Time Threshold report.
- Select the name of the service class that you want to view analysis
information. The list of all CICS transactions within that service
class displays. Then, select the transaction name that you want to
view the transaction analysis information.
- The Transaction Analysis view displays with the following
information calculating from the latest data that is collected within
the default timeframe that is set when you create the collection.
For more information, see OMEGAMON for CICS related reports and information.
- Maximum execution count
- Maximum CPU time
- Maximum response time
- Number of transactions exceeding goal response time
- Average response time and average response time trends
- Average DB2 and File I/O Wait Time of Response Time trends
- Average Execution count and average execution count trends
- Average CPU time and average CPU time trends
- Hover over the trend line to view data on that trend line.
- Observe the warning icon on top of the average response time trends.
The icon indicates the time where the maximum response time occurs.
- Observe the DB2 and File I/O wait time trends to see the area
where the DB2 or File I/O wait time is above the red line which is
the acceptable value. Currently it is set to 50%.
- Select different timeframe, for example, Hourly, Daily or Weekly,
on top of the trend chart to zoom in or zoom out information.
- If you associated Application Discovery
data provider with this workbook, you can perform deep analysis of
your performance issues based on the Application Discovery metrics
by performing one of the actions below.
Note: The analysis can be done
only when there are transactions with the same name on both OMEGAMON
for CICS and Application Discovery data.
- Analyze the potential artifacts that are cause of the performance
issues.
- Click on the area of the Average response time trends where you
want to do deep analysis. The dialogue box with Performance data appears.
- Click OK to navigate to the Artifact Composition graph.
The Artifact Composition graph appears with artifacts that connect
to either DB2 or File I/O. This depends on if the potential cause
is due to DB2 wait time or File I/O wait time. For example, if DB2
wait time is much above the acceptable value, the slow response time
can be caused by the DB2 wait time. The Artifact Composition graph
will display all the artifacts that connect to DB2 wait time.
- Analyze all artifacts within the transaction:
- Clicking on the Artifact Composition button on the top right of
the Transaction Analysis view. The Artifact Composition graph appears
with all artifacts within the Transaction. For more information about
how to analyze Artifact Composition, see Analyzing the Artifact Composition.