Multiple Code coverage invocations

Depending on how your software development process is set up, the convenience of having the AKGCC procedure take care of everything might not outweigh the resource and time usage to start a Code coverage collector for each program analysis.

Note: In version 15.0, this feature is moved to the z/OS® Debugger code.

z/OS Debugger provides the ccstart script to start a Code coverage collector which remains active. This collector can then be used in multiple Code coverage invocations. The ccstop script can be used to stop the collector.

These scripts (ccstart, ccstop, and codecov) are located in /usr/lpp/IBM/debug/headless-code-coverage/bin/ if you installed z/OS Debugger in the default location. For usage of these scripts, see Running code coverage in headless mode by using a daemon in the IBM® Developer for z/OS Knowledge Center.

The following is a generic usage scenario:
  1. Invoke ccstart with option to use a fixed port number and option to redirect the output to a known location.
  2. Invoke, as often as needed, programs to be analyzed with startup option.TEST(,,,TCPIP&<hostip>:<port>).
  3. Invoke ccstop.
  4. Direct the Developer for z/OS client to the output location to see the reports.