Using Code Coverage tab

A Code Debug session can optionally be code-covered using Code Coverage. Code Debug captures information about the test, including tracking which verbs and branches were taken. Reports can also be generated from Code Coverage. Mainframe reporting can be selected from the Code Coverage option from the Code Debug TSO primary menu. Code Coverage results can be displayed in the Workbench for Eclipse Code Coverage perspective.

To complete the Code Coverage tab

1. Select the Collect Code Coverage check box to activate standard Code Coverage. When selected, the Repository, System, and Test ID fields are enabled. The default for this check box is cleared.
2. From the Repository list, specify the dataset where Code Debug will write coverage information. This repository can then be used when creating a code coverage report request in the Workbench for Eclipse Code Coverage perspective..
3. From the System name list, type, select from the list, or browse to the system name for this test. When browsing, the Browse Repository dialog box appears. Select the system from the list. Code Coverage keeps statistics by programs separate by system name. This name can be any user-specified name.
4. From the Test ID list, type, select from the list, or browse to the test identification to be added to the Code Coverage test. When browsing, the Browse Repository dialog box appears. Select the test ID from the list. This information can be useful when reviewing test reports from Xpediter/Code Coverage.
5. Select the Clear existing statistics before starting the debug session check box to remove any data from previous code coverage collections for the selected repository, system, and test ID before executing the launch configuration.
6. Select the Display a report after the debug session check box to display a Code Coverage report when the debug session ends or is terminated.
7. Toggle open Test Data Optimization to show the fields below. This section is disabled if the Collect Code Coverage check box is not selected.
8. Select the Enable Test Data Optimization (TDO) check box to enable Test Data Optimization (TDO) for a test. TDO information can only be collected during a Code Debug TSO or Code Debug IMS test for a program with Code Coverage active. The TDO Dataset group box becomes active for entry when this check box is selected. The default for this check box is cleared.
9. In the TDO dataset field, specify the name of the dataset to be created or deleted, or click Browse to navigate to it. The name can be qualified with quotes or be unqualified. An unqualified name appears with your user ID as a prefix. Ensure that your site’s Code Coverage users have to write access to the specified dataset. If this field is left blank, Code Debug generates a DSNAME in the form userid.XPTDO.mmmdd.Thhmmss where, mmm is the three-character month, dd is the current date, hhmmss is the current time of day, in hours, minutes, and seconds.
10. In the Data class field, specify the desired SMS management class. Only use this optional field or the Storage class field when creating an SMS-managed dataset. When you use this field, leave the Volume and Unit fields blank. The appropriate values for those fields will be assigned by the system.
11. In the Storage class field, specify the desired SMS storage class. Only use this optional field when creating an SMS-managed dataset. When you use this field, leave the Volume and Unit fields blank. The appropriate values for those parameters will be assigned by the system.
12. From the Space units list, specify the primary space units for the dataset. A value must be entered when any dataset is created or deleted. Valid values are cylinders (CYL) and tracks (TRK).
13. In the Unit field specify the generic unit name on which to allocate the TDO dataset. If you specify a unit name, a sequential dataset will be dynamically allocated to a volume on that unit.
14. In the Primary field, specify the number of primary space units to be allocated for the TDO dataset. A valid space unit value must be entered when any TDO dataset is created.
15. In the Volume field, specify the volume serial number on which to allocate the TDO dataset. You can also specify a generic unit name. Only use this optional field when creating a non-SMS dataset. If you use the Storage Class field when creating an SMS-managed dataset, leave this field blank so that the system assigns the appropriate value.
16. In the Secondary field, specify the number of primary space units to be allocated for the dataset. A valid space unit value must be entered when any repository dataset is created.
17. In the Before test list, select APPEND to append data to the end of the existing TDO dataset or select DELETE to delete the existing TDO dataset and reallocate it.