Tools for troubleshooting scriptable code coverage

A variety of troubleshooting tools are available to help you diagnose and resolve product problems for scriptable code coverage support.

HTTP error code

If an error occurs when you make a REST service call to the z/TPF system, the service returns an HTTP status code that indicates the error. For more information about the error, see the description about the status code in the OpenAPI descriptor of the API (ccv.tpf.swagger.json).

z/TPF online messages

If an error occurs after the z/TPF system successfully accepts your REST service request but the z/TPF system fails to call the host on Linux® on IBM Z®, the error is displayed as an online message in the z/TPF console.

Remote formatting only: Apache Tomcat logging facility

If an error occurs after the z/TPF system successfully accepts your REST service request and the z/TPF system can successfully call the host on Linux on IBM Z, the Apache Tomcat logging facility logs the error in the log file of the scriptable code coverage convert web application. By default, the log file is stored in the tomcat/logs/ directory. Your system administrator might configure a different directory to contain the log file. If you cannot find the log file, contact your system administrator.

Native formatting only: tpfccv service logging facility

By default, the tpfccv service logs error and warning messages in the tpfccv.log file. You can view the location of the log file directory by entering zjamc display n-tpfccv.

The tpfccv service uses rolling log files. The most recent messages are in the tpfccv.log file. Earlier messages are in numbered log files, for example, tpfccv-1.log.

You can change the default tpfccv service logging by loading a customized log4j2.xml configuration file. For example, you can change the logging level to include debug messages in the tpfccv.log file:

  1. Stop the tpfccv service by entering the zjamc stop n-tpfccv.
  2. Make a local copy of the /base/tpfccv/resources/log4j2.xml file.
  3. In the log4j2.xml file, change the Root level element from info to debug, for example, <Root level="debug">.
  4. Load the local copy to the /sys/tpf_pbfiles/apps/tpfccv directory on the z/TPF system. Ensure that the tpfccv JAM application has the permissions to use the log4j2.xml file on the z/TPF system. For the permissions that you can set on the log4j2.xml file, see the base/cntl/tpfccvrest.loadfile file.
  5. Start the tpfccv service by entering the zjamc start n-tpfccv.
  6. Run scriptable code coverage services that use native formatting.
  7. Review the tpfccv.log file.

For more information about automatic configuration of Apache Log4j 2, see Apache Log4j 2.

ZDBUG CODECOVERAGE command

The ZDBUG CODECOVERAGE command can be used to display the details about the usage of scriptable code coverage services on the z/TPF system, including the number of completed and failed requests and requests in total. You also can use this command to clear registration entries and all relevant data for scriptable code coverage.