Starting z/OS Debugger Code Coverage
You can use IBM z/OS Debugger JCL Wizard to create JCL statements to generate code coverage data.
Code coverage aggregates statement execution information from multiple executions of a program.
This information can be used to depict any statements that were not tested. This function is limited
to Enterprise COBOL programs compiled with TEST(SEPARATE)
, Enterprise PL/I programs
compiled with TEST(SEPARATE)
, and z/OS XL C programs compiled with
DEBUG(FORMAT(DWARF))
. Your programs must be compiled with Enterprise COBOL or PL/I
with the appropriate options to create a separate SYSDEBUG file.
- Without a debug session.
- With a debug session on the 3270 interface using the code coverage indicator.
- A customized z/OS Debugger EQAOPTS module to
identify the z/OS Debugger
Code Coverage files is in the
load module search path
or
- The installer sets the variable
CODE_COVERAGE_SETUP = YES
in theEQAJCL exec
, which generates the following statements://EQAOPTS DD * EQAXOPT CCPROGSELECTDSN,'&&USERID.DBGTOOL.CCPRGSEL' EQAXOPT CCOUTPUTDSN,'&&USERID.DBGTOOL.CCOUTPUT' EQAXOPT CCOUTPUTDSNALLOC,'MGMTCLAS(STANDARD) + STORCLAS(DEFAULT) LRECL(255) BLKSIZE(0) RECFM(V,B) + DSORG(PS) SPACE(2,2) CYL' EQAXOPT END
CODE_COVERAGE_SETUP = YES
. When this value is specified, the EQAOPTS
DD
statements shown above are generated to create the appropriate file properties for
z/OS Debugger
Code Coverage. For information about what compilers are supported and which compiler options are required, see z/OS Debugger Code Coverage (Deprecated).