Milestone 5: Configuring Code Coverage — Upgrade

This milestone provides information about the configuration of an upgrade to Code Coverage 17.02.

If you are performing a new installation instead, go to Milestone 6.

This milestone involves the Code Coverage Installer.

Complete the tasks in this milestone to configure an upgrade to Code Coverage:

Task 5.1: Update ISPF support

If you are using Code Coverage with Code Debug TSO and Code Debug IMS, see to the Code Debug TSO and IMS Installation and Configuration Space, for instructions about configuring XPLIBDEF with Code Coverage.

Task 5.1.1  ISPF Support

If you had modified your TSO logon PROC for use with Code Coverage, you need to ensure that the correct (new) data sets are specified.

The recommended method is via the LIBDEF command. Copy SLXVSAMP members XPCOVER and XVTTCGDN into a library in your SYSPROC concatenation.

This CLIST library must be allocated to your ISPF session.

By default, the XPCOVER CLIST uses the Simple Deploy method to allocate the data set names specified in the CSMC PARMLIB DDSN* member (DDSN00 by default). If you are not using the default member, make sure to point to the DDSN* member name by setting the DDSNSFX keyword to the one- to four-character PARMLIB member suffix.

In addition, the primary CMSC will be used by default. If you are not using the default CMSC, specify the CMSC to use by setting the CMSC keyword to the one- to four-character CMSC ID

The XPCOVER CLIST can alternately use High-Level Qualifiers (HLQ) to allocate the Code Coverage data sets it references. For more information, see the comments in the CLIST.

Task 5.2: Upgrade Code Coverage with Code Debug CICS

If you are not using Code Coverage with Code Debug CICS, go to Milestone 8.

Follow these steps:

1. Modify JCL template data set for CICS.
   Review the XV.XVTCEXTJ data set in the STEPLIB. DSNs may need to be updated to specify the new SLXVLOAD and SLCXLOAD data sets.

   Warning

   A single JCL template data set can be shared by Code Debug CICS multiple CICS regions if the DSN for the template data set is specified in the resource definition to allow CICS to dynamically allocate and deallocate this file.

2. Update the CICS startup JCL.
   Change your site's CICS startup JCL by adding the load library containing Code Coverage to the DFHRPL concatenation. CPWR.MLXV170.SLXVLOAD is the default name for this loadlib.
3. Covert global table override input.
   If you are a current Code Coverage customer utilizing the XVGBLINP DD to specify global table overrides, be aware that you will have to convert your input to use the BMC PARMLIB. You must move your current override members from the data sets in the XVGBLINP DD into new members with the names of XVGBxxxx in the BMC PARMLIB. You can remove the XVGBLINP DD, which will no longer be needed, from your CICS JCL at your convenience.You will now use the BMC PARMLIB Index Member, XD$$00, to specify the members and order of concatenation for each CICS region in which you have Code Coverage installed. This member will be read during product initialization and provides the order of members to be read during product initialization or when the XVSI transaction is used to refresh parameter changes.

For more information, see Milestone 3 and Milestone 7.