Code coverage reporting process

The following figure shows the process for creating a XML report of the code coverage results. The report can be created by using batch facilities or by using IBM® z/OS® Debugger Utilities Option E.5 suboption 1. The input to the report utility is the Selection file that is created by the user in the Step 2. Code Coverage selection and extraction process, the resulting data set from that process, and the Code Coverage extracted observations data set.

The code coverage XML report process is as follows:

1. The code coverage Report Utility uses the code coverage extracted observations that are created after you apply the selection criteria to create the code coverage report.
2. The code coverage Report Utility also uses the Selection file that is created by using DTU Option E.3 or coded manually by following the Selection file XML DTD syntax to include only the selection criteria as part of the report.
3. You can start the code coverage Report Utility from DTU Option E.5 suboption 1. When you select this option, you can provide the name of the Selection file, the extracted Observation file, and the file where the XML report is stored.
4. The code coverage Report Utility can be run in batch as well by running the EQAXCCR2 REXX exec with the XML parameter. You must specify the following DDNAMES:

   EQACRINP

   Code coverage extracted observations that are based on selection criteria.

   EQACRSEL

   Code coverage Selection file.

   EQACROUT

   XML report output.

An example of using EQAXCCR2 in batch to generate a XML report can be found in hlq.SEQASAMP(EQACCXRP).

In addition to the XML report, you can also generate a Presentation report. This is generated by selecting DTU Option E.5 sub-option 2 or 3. In batch specify the PFMT parameter. An example of using EQAXCCR2 in batch to generate a Presentation report can be found in hlq.SEQASAMP(EQACCPRP).