Specifying code coverage options in the startup key

When running code coverage in the client or in headless mode, code coverage options can be directly specified in the startup key. In the case of the client, this allows the user to specify code coverage options prior to the creation of a launch configuration. If the launch configuration already exists, then the startup key options override any settings in the launch configuration. In the case of headless mode, specifying startup key options allows the user to override daemon settings.

About this task

You can specify a number of code coverage options from within your JCL by including them in the startup key.

Procedure

Edit your JCL and modify the startup key. For example, to specify function level coverage:
// PARM.RUN=('/TEST(,,,TCPIP&&<IP_address_for_RDz_client>%<port_for_RDz_debug_UI_daemon>:*)')
//******* ADDITIONAL RUNTIME JCL HERE ******
//CEEOPTS   DD *
 ENVAR("AQE_DBG_V4LIST=//'USER.COBOL.LISTING'",
 "AQE_STARTUP_KEY=CC,PRTPRIM,cclevel=FUNCTION",
 "AQE_DBG_TRACE=/home/user/probe.trc")
/*
//CEEDUMP   DD SYSOUT=*
Note: This example uses the AQE_STARTUP_KEY environment variable. Environment variables whose names begin with AQE are used with the Rational® Developer for System z® Integrated Debugger. If you are using the Debug Tool, use EQA environment variables. For information about generating JCL code, see the related link Runtime step options.
Property Valid Values Description
cclevel MODULE, FUNCTION or LINE Code coverage level
modulelist path The path to a file which contains the list of modules to include in a module level report.
moduleexcludelist path The path to a file which contains the list of modules to exclude from a code coverage report. Modules should be listed one per line, and the file may contain regular expressions.
prevresultpath path The path to a previous result.
reportformat HTML, NONE Report format, specify HTML to generate an HTML report in addition to the workbench report.
startupcommandlist NONE, PREV, path The path to a file which contains debug startup commands. Commands should be listed one per line within the file.
savesource TRUE, FALSE Whether or not source should be saved for the code coverage session.
tag A string of alpha-numeric characters A list of tags to associate with the code coverage result. Multiple tags should be enclosed in quotes and separated by a comma (,).
testid A string of alpha-numeric characters Test id
timeout An integer Number of seconds to wait for a debug engine response before timing out. The default is 120 seconds. The session will terminate and results already captured will be saved. Specifying 0 (zero) will wait indefinitely.

Feedback