Code coverage selection and extraction process

The following figure shows the selection and extraction process. In this process, a code coverage Observation file that is created during a z/OS® Debugger Code Coverage session is evaluated using a Selection file. The Selection file is provided by the user, and it indicates the type and granularity of the code coverage extracted observations that must be extracted from the original Observation file. For example, you want a report for only a program with a specific compile time and date. The Selection file can be created using IBM® z/OS Debugger Utilities Option E.3. Alternatively, you can code a Selection file by following the Selection file XML DTD syntax.

Figure 1. Step 2 Code coverage selection and extraction process
Step 2 Code coverage selection and extraction process

The code coverage selection and extraction process is as follows:

  1. The code coverage Extraction Utility operates on the observations and applies the selection criteria to create a file with extracted observations based on the selections.
  2. The Selection file can be created using IBM z/OS Debugger Utilities Option E.3. Alternatively, you can code a Selection file by following the Selection file XML DTD syntax.
  3. You can run the code coverage Extraction Utility from DTU E.4. When you select this option, you are prompted to provide the name of the selection file, the Observation file, and the file where the code coverage extracted observations are stored.
  4. You can run the code coverage Extraction Utility in batch as well by running the EQAXCCX2 REXX exec. You must specify the following DDNAMES:
    EQACSINP
    Location of Observation file.
    EQACSSEL
    Location of Selection file.
    EQACSOUT
    Location of output code coverage extracted observations file.

    An example of using EQAXCCX2 in batch can be found in hlq.SEQASAMP(EQACCEXT).