Milestone 7: Using BMC PARMLIB to configure Code Coverage with Code Debug CICS

Specifying Code Coverage parameters at product initialization

Code Coverage includes a facility that allows you to override the current parameter settings in the XVTCGBL load module at product initialization. This facility can also be invoked while Code Coverage is active by entering the transaction XVSI. For complete information, see to Overriding Parameters.

When overriding the parameters, a BMC PARMLIB report (Code Coverage Parameters) is written to a transient data queue. The default queue name is XVGR, which should have been defined using RDO when Code Debug CICS was installed. See to Step 1 in Task 4.4.1 Using RDO to Update Resource Definitions in the Code Debug CICS Installation and Configuration Space.

Parameter ineligible for XVSI transaction

The LOG_TDQ_NAME parameter can't be overridden with the XVSI transaction. It may, however, be overridden when Code Coverage begins initialization. For more information, see Overriding Parameters.

Global parameter default values and descriptions

The following table lists all the BMC PARMLIB parameters related to Code Coverage with Code Debug CICS, PARMLIB Version 1 parameter names, and the default values for each. Detailed descriptions of all the parameters are provided in the Parameter Descriptions section of this Milestone.

Global parameters

PARMLIB parameter	PARMLIB version 1 parameter	Default in XVTCGBL
AUTO_SUBMIT_JCL_DURING_EXTRACTION	SUBMIT	YES
CAPTURE_SYSTEM_FLOW_USING_GMT_TIME	CTLGMT	YES
CODE_COVERAGE_PARMLIB_REPORT_ALLOCATION	Deprecated
CODE_COVERAGE_PARMLIB_REPORT_DDNAME	XVGBLRP	XVGR
CODE_COVERAGE_PARMLIB_REPORT_SYSOUT_CLS	Deprecated
DATA_EXTRACTION_INTERVAL	INTERVAL	42
INCREMENT_VERB_COUNTS	COUNT	YES
KEEP_PROGRAM_COUNTS_FOR_USERID	PROGCNTS	*******
LOG_INFO_MESSAGES	WTDQ	YES
LOG_TDQ_NAME	LOGQ	CSM1
PRIME_OWNER_FILTER_WITH_CURRENT_USERID	FILTDEFU	NO
TRANSID_XVCC	XVCC	XVCC
TRANSID_XVKP	XVKP	XVKP
TRANSID_XVSC	XVSC	XVSC
TRANSID_XVSI	XVSI	XVSI
TRANSID_XVTQ	XVTQ	XVTQ
WRITE_DATA_EXTRACTION_MSGS_TO_JES_LOG	WTO	YES

Parameter descriptions

This topic describes each parameter. The default values are listed are those in XVTCGBL.

AUTO_SUBMIT_JCL_DURING_EXTRACTION

Default: YES
Automatically submit the Code Coverage template JCL during extraction. Enter NO to disable the automatic submission during extraction. If AUTO_SUBMIT_JCL_DURING_EXTRACTION is set to NO, the JCL to write the extracted data to the Code Coverage repository would need to be submitted manually.

CAPTURE_SYSTEM_FLOW_USING_GMT_TIME

Default: YES
Optionally capture System Flow data with local time
(CAPTURE_SYSTEM_FLOW_USING_GMT_TIME=NO). Specifying
CAPTURE_SYSTEM_FLOW_USING_GMT_TIME=YES will capture System Flow data with GMT/UTC.

CODE_COVERAGE_PARMLIB_REPORT_ALLOCATION

This parameter has been deprecated.

CODE_COVERAGE_PARMLIB_REPORT_DDNAME

Default: XVGR
A one- to four-character transient data queue name that the BMC PARMLIB report ( Code Coverage Parameters) is written to.

CODE_COVERAGE_PARMLIB_REPORT_SYSOUT_CLS

This parameter has been deprecated.

DATA_EXTRACTION_INTERVAL

Default: 42

The number of minutes between automatic data extractions. Valid values are from 1 to 1440.

INCREMENT_VERB_COUNTS

Default: YES
Set this option to NO when it is not necessary to count each time a verb is executed. When INCREMENT_VERB_COUNTS=NO, Code Coverage will count each verb only the first time it is executed. To maximize the potential performance benefit of INCREMENT_VERB_COUNTS=NO, rules for Storage Protection and Program Trace are ignored when INCREMENT_VERB_COUNTS=NO and a Code Coverage test is active.

Important

When parameter INCREMENT_VERB_COUNTS=NO, the System Flow feature of Code Coverage cannot be used. An error message is displayed if you attempt to activate either System Flow or both (Code Coverage plus System Flow).

Warning

When INCREMENT_VERB_COUNTS is set to NO:

Only one Code Coverage test at a time may be active in the CICS region.
Each application program you execute is marked as RESIDENT until every verb within it has been executed or the Code Coverage test has been halted. If you encounter a Short on Storage (SOS) situation using INCREMENT_VERB_COUNTS=NO, reduce the number of programs referenced by your Code Coverage test.
CPU consumption may actually increase, depending on the structure of your Code Coverage test. When the same code is executed multiple times, INCREMENT_VERB_COUNTS=NO will reduce CPU consumption by a factor related to how many times the code is executed. However, when different code is executed by each transaction and there is very little reuse of the same code, INCREMENT_VERB_COUNTS=NO can cause a noticeable increase in CPU consumption.

KEEP_PROGRAM_COUNTS_FOR_USERID

Default: ********
Specifying KEEP_PROGRAM_COUNTS_FOR_USERID=******** causes program counts for a program to be kept separate by userID. Specifying KEEP_PROGRAM_COUNTS_FOR_USERID=USER1234 causes program counts to be kept under userID USER1234 for programs being covered, regardless of the userIDs that executed the programs.

LOG_INFO_MESSAGES

Default: YES
Used to disable the write to transient data queue function for Informational Data Extraction messages (XVTC4nnnI). The queue name is specified by the LOG_TDQ_NAME parameter. Enter NO to disable.

LOG_TDQ_NAME

Default: CSMT
The four-character name of the transient data queue to which Code Coverage is to direct error messages. This parameter cannot be changed when Code Coverage is active. It may be changed at Code Coverage initialization when the BMC PARMLIB is initially processed.

PRIME_OWNER_FILTER_WITH_CURRENT_USERID

Default: NO

Prime the Owner column filter value with the current userID
(PRIME_OWNER_FILTER_WITH_CURRENT_USERID=YES). Prime the Owner column filter with asterisks (PRIME_OWNER_FILTER_WITH_CURRENT_USERID=NO).

TRANSID_XVCC

Default: XVCC
A four-character transaction ID to substitute for the XVCC transaction. Changing the value requires changing the supplied resource definition.

TRANSID_XVKP

Default: XVKP
A four-character transaction ID to substitute for the XVKP transaction. Changing the value requires changing the supplied resource definition.

Warning

XVKP is an internal transaction that you should never enter from a terminal. Also, because the XVKP transaction is run asynchronously, security should not be set on it.

TRANSID_XVSC

Default: XVSC
A four-character transaction ID to substitute for the XVSC transaction. Changing the value requires changing the supplied resource definition.

TRANSID_XVSI

Default: XVSI
A four-character transaction ID to substitute for the XVSI transaction. Changing the value requires changing the supplied resource definition.

TRANSID_XVTQ

Default: XVTQ
A four-character transaction ID to substitute for the XVTQ transaction. Changing the value requires changing the supplied resource definition.

WRITE_DATA_EXTRACTION_MSGS_TO_JES_LOG

Default: YES
Used to disable the write-to-operator (WTO) function for the XVTC4001 Data Extraction complete message and other Informational Data Extraction messages (XVTC4nnnI). A WTO is normally issued each time a data extraction is performed. Enter NO to disable.

This section provides information about the following topics: