Overriding parameters

This topic explains how to override Code Coverage's parameters specified in the XVTCGBL load module.

Overriding parameters using the BMC PARMLIB

This preferred method reads the desired parameter values from the BMC PARMLIB during product initialization. This method is easy to set up and maintain, and it makes Code Coverage itself easier to install and maintain. See to Milestone 3: BMC PARMLIB Implementation in the Code Debug CICS Installation and Configuration Guide and PARMLIB Members in the Code Debug CICS Advanced Configuration Space for specific information.

In addition, a stand-alone transaction, XVSI, can be used to read the parameters from the BMC PARMLIB. This eliminates the need to recycle Code Coverage or the CICS region when you want to make parameter changes. If an error is detected in a parameter, processing continues and an error message is written to the output report. See to the Code Debug CICS Messages and Codes for a list of possible messages.

This section includes information about the following topics:

• Processing of the parameters
• Overriding report data set ddname
• Format of the override report and console log output.

Defining Output Report Parameters contains step by step instructions for defining the attributes for the Report Data set produced during the override process, using the BMC PARMLIB.

Concatenation of BMC PARMLIB members

The BMC PARMLIB Index Member XD$$00 provides the ability to concatenate members in the same fashion as sequential data set DDs. See to the section Creating Additional Members for Region Customization entitled in theCode Debug CICS Advanced Configuration Space.

Processing overview

Override parameters are read from the BMC PARMLIB.

As the input is processed, a BMC PARMLIB Report (Code Coverage Parameters) is written to a transient data queue which must be defined as Extrapartition. The default queue name for this report is XGBR. The CODE_COVERAGE_PARMLIB_REPORT_DDNAME configuration parameter can be used to change the name of the report queue.

Parameters are processed in the order in which they are read. Blank records and comment records are ignored. As each parameter is processed, it is written to the output report. See Adding Parameters to a Member in the BMC PARMLIB for parameter format and processing rules.

If an error is detected in a parameter override, processing continues and an error message is written to the output report. See to the Code Debug CICS Messages and Codes space for a list of possible messages.

CICS Code Coverage parameter report

The CICS Code Coverage Parameter report is written to a transient data queue with a default name of XVGR. If the queue is not defined, processing will continue, but no report will be produced.

The following figures provide more information about the sample CICS Code Coverage Parameter report. The highlighted numbered references are discussed following the figures.

CICS Code Coverage Parameters Report Page 1

[1] The third heading line indicates the CICS region applid, date, time, terminal, and userID of the user logged on to the terminal when program XVTCSIT was run.

[2] These heading lines indicate the transient data queue used for the report. In addition, they indicate whether the queue used is the default name or has been overridden by the user.

[3] Input parameters are displayed from here down. This provides a complete audit of the parameters processed.

[4] Comments in the BMC PARMLIB member are not displayed.

[5] The CMSC ID of the BMC PARMLIB where the memory objects reside.

[6] The data set where the memory object for XD$$00 was refreshed from.

[7] The concatenation order of the input members to be processed as derived from the index member XD$$00.

[8] A comment box precedes the data for each CMSC memory object read. It will display the data set where the memory object was refreshed from.

CICS Code Coverage parameter log output

Messages are written to the console log whenever the CICS Code Coverage Parameter process is run. In addition to messages indicating the start and end of processing, any errors related to data set attributes are also written to the console. The following figure shows a sample of output written to the console.

Messages that do not apply to a particular input parameter are displayed with two lines per message. All messages contain similar information on the first line including a message number, severity level, date, time, and region applied.

Sample CICS Code Coverage Parameter Input, Console Log Output

In addition to the console log output above, the input processing program for the CICS Code Coverage Parameters process will display additional informational and error messages in the CICS CSMT output queue. The following figure is a sample display of messages that can be output. In this sample, an error was detected. Member XVGBXX was not found in the BMC PARMLIB.

Sample CICS Code Coverage Parameter Input, CSMT Output