The code review application for Windows: FAQs and troubleshooting

Access the product documentation on the web, get answers to frequently asked questions, and learn how to troubleshoot common problems for the code review application.

Documentation

The product documentation is available on the web at Developer for z/OS®.

FAQs: Frequently asked questions

  1. Why is the code review application generating so many different types of data files? Are there options to generate only certain types?

    The code review application always generates all the types of data files that are available. The types of data files must be registered with Eclipse and must apply to the programming language or languages in which the specified source code files are written.

  2. Why does the output information display a strange URL such as [url]http://server:9090/rsar/reports/20121004_162226/[/url] ?

    See Information written to standard output.

Troubleshooting

  1. When I run the code review application, no output information is written to standard output. How can I get the application to produce this information?
    Follow these steps:
    • If you are using Windows:
      1. Verify that you are using the parameter -verbose.
      2. Verify also that you are redirecting standard output to an output file on the command line. See the descriptions of the -verbose parameter and the output file.
    • All or part of the output information can be missing for the following reasons. The reasons apply if you are using Windows but you already verified the -verbose parameter:
      • A path that you are passing as a parameter to the application is not correct.
      • The project or directory that you specified does not contain any source code files.
      • The rules in the rule file do not apply to any of the source code files that you are analyzing.
    • Try to use the sample script to run an analysis similar to the one that is not working for you. Turn on the -debug option of the sample script to print output information to the screen. If the sample script produces the correct output, compare it to your invocation to spot the problem.
  2. Why do the paths in the output files contain prefixes such as genericProject_ and analyzedAsJava_?

    When you use the -directory parameter, the code review application creates a temporary project in the workspace that is specified in the -data parameter. The temporary project folders have prefixes such as genericProject_ or analyzedAsJava_, for each directory specified. See Deleting temporary projects created by the -directory parameter.