Milestone 8: Specifying System Facilities and Code Coverage Test Parameters

This milestone explains how to specify the parameters used to specify the Code Debug CICS System Facilities and Code Coverage Test parameters (formerly DBPA Input).

Code Debug CICS uses BMC PARMLIB members to define System Facilities and Code Coverage Test options during product initialization. The BMC PARMLIB with the desired parameters is read at Code Debug CICS startup.

All you need to do is create a member, XDDB00, in the BMC PARMLIB that contains the System Facilities and Code Coverage Test parameters you wish to process. Comments and blank lines are allowed within your parameters. A report echoes the input parameters and provides any error messages. See to Implement the BMC PARMLIB.

Transaction XDBP can be used to refresh the parameters from the BMC PARMLIB. This eliminates the need to recycle Code Debug or the CICS region when you want to make storage protection option changes.

This task includes sections on the following topics:

• Processing of the parameters
• Overriding the report transient data queue name
• Format of the parameter processing report and console log output

If your site uses Code Coverage, this method can also be used to define Code Coverage tests. For details, see “Code Coverage Test Parameters” in the Code Coverage Mainframe User/Reference Guide.

Task 8.2 Processing Overview

System Facilities and Code Coverage Test parameters are read from the BMC PARMLIB.

As the input is processed, a BMC PARMLIB Report (Code Debug CICS System Facilities and Code Coverage Test Parameters) is written to a transient data queue which must be defined as Extrapartition. The default queue name for this report is XDBR. The DBPA_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. Parameter images are also written to the output report.

If an error is detected in a parameter, the record - along with an error message - is written to the report. For a list of possible messages, see to the Code Debug CICS Messages and Codes.

Task 8.3 Code Debug CICS System Facilities and Code Coverage Test Parameters Report

The following figure is a sample Code Debug CICS System Facilities and Code Coverage Test report. The highlighted numbered references are discussed following the figure.

Sample Code Debug CICS System Facilities and Code Coverage Test Parameters Report

[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 DBUGDBPA 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 and member name.

[9] When an error is detected on an input record, the error is flagged. The line that follows contains a message indicating the error detected and is also flagged. Only the first error detected for a parameter is flagged.

Task 8.4 Code Debug CICS System Facilities and Code Coverage Test Parameters Log Output

Messages are written to the console log whenever the Code Debug CICS System Facilities and Code Coverage Test Parameters process is run. The following figure is a sample of output written to the console.

Messages that do not apply to a particular System Facilities and Code Coverage Test 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 applid. This provides two places that can be checked for error conditions. Messages that apply to a particular System Facilities and Code Coverage Test parameter are displayed with three lines per message. The second line contains the first 71 bytes of the input image. The third line contains the message text.

Sample Code Debug CICS System Facilities and Code Coverage Test Parameters Input, Console Log Output

In addition to the console log output shown in above figure, the input processing program for the global override process will display additional informational and error messages in the CICS CSMT output queue. The following figure provides a sample display of messages that can be output.

Sample Code Debug CICS System Facilities and Code Coverage Test Parameters Input, CICS CSMT Output Queue Messages