Defining output report parameters

This topic describes the steps necessary to create parameters to override the parameter settings in the XVTCGBL load module. These parameters will be read during product initialization to allow modification of global table settings.

A stand-alone transaction, XVSI, can be used to refresh the parameters from the BMC PARMLIB once Code Coverage has completed initialization. This eliminates the need to recycle Code Coverage when you want to make parameter changes. Even if you don't need to modify parameters at this time, we recommend that you use the skeleton member created in this procedure. Nothing will be harmed, and if you later need to modify parameters, they will be ready for use.

Using the BMC PARMLIB to specify parameters has several advantages. They include ease of installation, flexibility in maintenance of input, and the ability to modify the parameters while the region is active.

Setting up the BMC PARMLIB parameters

Perform the following steps to establish parameter processing:

1. Create the default member in the BMC PARMLIB.
   
   1. Create a new member, XVGB00, in the BMC PARMLIB.
   2. Copy member XVGB00 from the SMXDSAMP library into it.

   3. Perform a refresh of this member. For more information, See to Milestone 3: BMC PARMLIB Implementation in the Code Debug CICS Installation and Configuration Guideand Overriding Parameters for additional instructions.
      This method of specifying parameters is very flexible. If you wanted to specify parameters for a specific CICS region, you could use the name XVGBsysi where sysi is the SYSID of the CICS Region. You could also create a single member for all regions. By using member concatenation as described in the section entitled Creating Additional Members for Region Customization inCode Debug CICS Advanced Configuration Space, you could create a set of members to control the process. You could have a member common to all regions, a member specifically for test regions, and a member for a single region.
      For example, XVGB00 contains a set of parameters common to all regions. Member XVGBTEST could contain parameters intended for test regions. Finally, member XVGB0001 would have parameters specifically for region CICS0001.

2. Specify the name of the report transient data queue name.
   Make sure the transient data queue (default name XVGR) has been installed. See to Step 1 in Task 4.1.4 BMC PARMLIB Reports in the Code Debug CICSInstallation and Configuration Guide. If the name was changed, write it in the space . Otherwise, just write in XVGR.
   Report transient data queue name: ____________________below

3. Modify the default override member XVGB00.
   Add the CODE_COVERAGE_PARMLIB_REPORT_DDNAME parameters that allow you to easily override the report transient data queue name.
   CODE_COVERAGE_PARMLIB_REPORT_DDNAME=name
   Modify the lines as follows:
   
   1. Change name to the value you wrote down in Step 2.
   2. Save the member, refresh it as described in PARMLIB Product Configuration, and continue.

PARMLIB product configuration

Use the z/OS MODIFY (F) command to update the BMC AMI Common Mainframe Services Controller (CMSC) with the PARMLIB members you created.

Refreshing a single parameter member

F cmscname,PARMLIB REFRESH member_name

Refreshing all PARMLIB members

F cmscname,PARMLIB REFRESH

Testing the setup

Setup of the global table parameter override facility is now complete.

When testing Code Coverage after installation, look for the global table override report data set in your JES output. Check the report, the console log, and the CICS and CSMT log output for any errors that may have occurred while overriding global table parameters. Message formats and explanations are provided in the Code Coverage Mainframe User/Reference Space and the Code Debug CICS Messages and Codesdocumentation.

Adding parameters to a member in the BMC PARMLIB

Parameters used by your BMC mainframe product or component are read from the BMC PARMLIB data set. Edit the sample parameters to your site's requirements, observing the recommendations in the following table:

General Parameter Editing Guidelines

PARM name	Values	Samples
Data columns	1 to 71	N/A
Symbol separator	Underscore	A_LONG_SYMBOL
Continuation	Check for + character in Column 72.	+
Comments	* in column 1 Between columns 1-71, begin with /* and end with / is a comment /* is a comment */	8 is a comment /* is a comment */