Task 4.1: Installing ISPF support

Testing with Code Coverage interactively might require an increase in the default TSO logon region size. Code Coverage requires about 250 K.

1. Create an ISPF logon PROC or CLIST.
2. Establish a way of allocating the Code Coverage data sets (such as .SLXVPENU or .SLXVSENU) to each user of Code Coverage. 
   The following are two suggested methods:

   • (Recommended) Use 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.

     Important

     You can display the libraries in your SYSPROC concatenation by entering the command TSO ISRDDN.

     By default, the XPCOVER CLIST will use 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.

     To point to PARMLIB member DDSNCPWR, use DDSNSFX(CPWR).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. 

     To point to CMSC subsystem TEST, use CMSC(TEST).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 

   • (Alternative) Modify or create TSO logon PROCs to concatenate Code Coverage libraries to the appropriate DD cards. The Code Coverage data sets listed in the following table must be concatenated into the listed ddnames. Replace CPWR.MLXV170 with the values used for the installation of Code Coverage.

     ISPF Support Dataset Concatenation

     ddname	Data set name
     SYSPROC	CPWR.MLXV170.SLXVCLIB
     ISPLLIB	CPWR.MLXV170.SLXVLOAD
     ISPMLIB	CPWR.MLXV170.SLXVMENU
     ISPPLIB	CPWR.MLXV170.SLXVPENU
     ISPSLIB	CPWR.MLXV170.SLXVSENU
     ISPTLIB	CPWR.MLXV170.SLXVTABL

3. If Code Debug CICS has been installed, add the following data sets for the Program Inventory Utility:

   Code Debug CICS Datasets for use with the Program Inventory Utility

   ddname	Data set Name
   ISPLLIB	CPWR.cMXDnnn.SMXDOxxL

4. Replace CPWR.MLXV170 with the values used for the installation of Code Coverage. Replace CPWR.cMXDnnn.SMXDOxxL, with the appropriate load library. See to the table Load Libraries for CICS Release Support in the Code Debug CICS Installation and Configuration Space for the default data set names.

5. If your site uses any security processing that restricts the programs that can be used as TSO commands, make sure the following programs are available to your users and are not affected by any such restrictions:
   • XVTTACMT
   • XVTTADSN
   • XVTTAENQ
   • XVTTAFGN
   • XVTTAFIL
   • XVTTAFLG
   • XVTTAJCL
   • XVTTAMNT
   • XVTTARGN
   • XVTTASDL
   • XVTTAU01
6. Provide a way to invoke the Code Coverage product.
   • If you pre-allocated all the required Code Coverage libraries, the basic ISPF (internal) subcommand needed to invoke the Code Coverage product is:
     SELECT CMD(XVTTCGO) NEWAPPL(XVTC) PASSLIB
   • If you tailored the XPCOVER CLIST and put it in the SYSPROC concatenation or activated it with an ALTLIB command, enter:
     SELECT CMD(%XPCOVER)
   • If you tailored the XPCOVER CLIST into some other library, enter:
     SELECT CMD(EXEC 'YOUR.LIBRARY.CLIST(XPCOVER)')

You also have options for specifying the SELECT command:

1. 
   
   • You can specify it as a part of a command table entry for a verb such as CODECOVR.
   • You can establish the command as an option by editing an ISPF panel. If you establish the command as a panel option, the following is recommended for the ISPF menu text:
     XV Code Coverage - Code Analysis and Program Report Generation Tool
     The following would be added to the processing section TRANS statement:
     XV, 'xxxx'
     xxxx is the parameter of the appropriate SELECT command described above (omitting the SELECT verb). For example, if you tailored the XPCOVER CLIST and put it in the SYSPROC concatenation as shown above, the following statement would be added to the processing section TRANS statement:
     XV CMD(%XPCOVER)

7. If Code Debug CICS has been installed, we recommend completing the following steps to ensure the availability of the Program Inventory Utility:

1. 
   
   1. After creating or modifying the logon PROC or CLIST for Code Coverage, enter Code Coverage and choose option 5 (ISPF option 0.5) from the Defaults menu.
   2. Enter the name of the default program inventory file for all users.
   3. Enter the name of the excludes file distributed with Code Debug CICS:
      CPWR.cMXDnnn.SMXDSAMP(POPEXCL)
      where nnn is the release of Code Debug CICS, and c designates the CICS release.
   4. Choose option 6 (Code Coverage option 0.6) from the Defaults menu and enter the names of all the default Code Debug CICS application load libraries.
   5. Choose option 7 (Code Coverage option 0.7) from the Defaults menu and enter the names of all the default Code Debug CICS source listing files.
   6. Access the ISPF Primary Option Menu, and select option 3.3 (Move, or copy members or data sets). Copy your profile (ISPFPROF) data set member XVTCPROF to CPWR.MLXV170.SLXVTABL, the new Code Coverage data set.
2. 8. If Code Debug TSOis installed and the JCL convert option is necessary, the CPWR.MLXV170.SLXVSENU data set member XVTTSJ02 must be tailored with the names of your ISPF data sets and the Code Debug TSO XOPTIONS data set name. Change the names to reflect your data sets. These data sets are marked with **TAILOR*** in the member.