After you run a code review, you can view the results that
are generated.
Before you begin
You must create a software analysis configuration
or baseline analysis configuration and run it.
About this task
The results of a code review are stored in an
analysis
history. In the
Software Analyzer Results view,
you can select an analysis history, view its contents, and save the
results to a file. When you run a code review, the software analyzer
automatically opens the
Software Analysis Results view
to display the results. You can also open the view manually.
Procedure
- To open the Software Analyzer Results view:
- Click .
- Click .
- Click OK.
The Software Analyzer Results view
opens. The left pane lists the analysis histories of the code reviews
run since the workbench was last opened.
The most recent analysis history is at the top of the list. Each
history is a compilation of the results from a single code review. Figure 1 shows an example of a list entry
for an analysis history. The entry contains the name of the analysis
configuration used (Cobol Tool Dev 041), the time and date of the
code review, the number of individual results in the history (38),
and the processing time for the code review (0 milliseconds):
Figure 1. Left pane: List entry
for an analysis history
- In the left pane, click the analysis history that you want
to view. The results in the history are displayed
in the right pane.
- Optional: To delete the history, right-click
the entry and click Delete.
- Optional: In the right pane, in the toolbar,
you can switch between two display modes:
- To display all the rules that you selected in the analysis
configuration, even if the code review found no violations of the
rule, click Show all selected rules and results
.
- To display only the selected rules for which the code review
found violations, click Show only rules with results
.
- Expand a rule that contains results and view the results. The results are grouped according to category (such as
Naming Convention and Performance), rule, source file name, and line
number.
Figure 2 shows an example of part of a listing.
In the figure, the rule category is Program Structures, a built-in
category. The rule is Avoid ACCEPT statements, a built-in rule, which
is assigned a severity of Warning, indicated by the icon

. Below the rule are listed two results that refer to a source
code location where a problem of this type was found. Each result
contains the severity icon of the rule, the source code file name,
the line number, and the text of the rule.
Figure 2. Right pane: List entry for an individual
result
What to do next
To fix a problem reported in a result, see Fixing a problem reported in a result.
To save any of the analysis histories that
are displayed in the Software Analyzer Results view,
generate a report or open the analysis history in a browser and save
it to a file on your workstation. For more information about generating
and saving reports, see Generating and saving reports.