Release Notes

Xpediter/Code Coverage 3.1

August 1, 2016
Quantify the Thoroughness of Your Testing Efforts

Xpediter/Code Coverage is an advanced analysis tool that clearly and easily identifies how much of an application has or has not been executed. Code Coverage helps identify the percent of code executed for single or multiple programs, for one test or for multiple tests run over time, and from a high-level management view down to a single line of code.

Code Coverage works in conjunction with Compuware’s mainframe test and debugging tools Xpediter/CICS and Xpediter/TSO and Xpediter/IMS. As you perform your testing, Code Coverage keeps track of what parts of your code have been exercised and what parts have not. The results generated by Code Coverage can be displayed, analyzed, and output using Xpediter/DevEnterprise and Compuware Program Analyzer. You can also output detailed reports directly from Code Coverage on the mainframe.

Latest Release Notes

What’s New

Software and Hardware Requirements

Technical Notes

Known Issues

Product Documentation

Support Resources

Latest Release Notes

If you accessed this document from a product or documentation CD, you may not be reading the latest Release Notes. For the most recent information, go to FrontLine , Compuware's technical support Web site. The first time you access FrontLine, you are required to register and obtain a password. After logging onto FrontLine, select your product from the drop-down list and click Go. On the left side of the page, click the Documentation link. You will find the latest Release Notes listed with the other product documentation.


What’s New
Release Notes Standardization

The Software and Hardware Requirements section of the release notes has been standardized across all Compuware Mainframe products and their Distributed components. Please note that any versions of third-party software that are no longer supported by their vendors under standard published contracts have been removed from the Software and Hardware Requirements section and placed in the Discontinued Support section of the release notes. However, any third-party software that was supported when this Compuware product went GA will continue to be supported until this product release has reached its End of Support date. No functionality has been removed from the product.

Batch Program Test Data Optimization

When used in conjunction with Xpediter/TSO, Code Coverage will now provide a list of records, identified either by sequence number or index key, that are associated with first-time code execution. This provides a way for you to eliminate redundant test cases; i.e. “optimizing” your test data.

Note: Only COBOL programs using QSAM, VSAM, or IMS access methods are supported.

Low-Priority Code Exclusion

The previous release of Xpediter/Code Coverage provided the ability to identify “high-risk” code: new code that hadn’t yet been run in a production environment. It might be an entire program or added or changed code implemented during a maintenance task. This high-risk code is weighted more heavily when compiling the Relative Risk Metric for a program indicating how well it’s been tested. Xpediter/Code Coverage reporting, both on the mainframe and in the GUIs of Xpediter/DevEnterprise and Compuware Program Analyzer, highlights untested new code very clearly.

To complement that capability, Xpediter/Code Coverage users have been requesting some type of “low-risk” identification. Low-risk code could be commonly used utility modules or error routines that haven’t changed and have been reliable for years. Low-risk code might also be code that would be very difficult to test, such as time-outs on responses from other sources outside of the application or other conditions that can’t easily be created with test data.

The new Low-Priority Code Exclusion feature in Xpediter/Code Coverage gives you the ability to identify “low-risk” code and exclude it from reporting. Unexecuted low-risk code does not affect the Relative Risk Metric, having no effect on the reporting of tested and non-tested code counts and percentages.

This essentially adds a third level of code definition to Xpediter/Code Coverage, supplementing the existing high-risk and normal-risk levels found in earlier versions of Code Coverage.

Specification of low-risk code follows the existing methods already used for identifying high-risk code: code stamps or beginning/ending values used within the code, as well as “filters” to isolate and categorize the code accordingly.

Expanded Line Filters

Code Coverage’s Individual Line filters had previously been limited to eight characters in length. While this was adequate for “code stamps” placed in the areas reserved for comments by the compiler, Compuware learned that these filters were sometimes being used to describe data element names to be treated as high-risk code, and eight characters are not sufficient in many cases to uniquely identify those data elements. This enhancement expands the available Individual Line filter length to 50 characters.

Xpediter/Code Coverage’s Individual Line filtering capabilities are also being enhanced to provide “match on word” specification. With “match on word” specifically requested, a filter of “all” will return only the matches for the standalone word “all”. Without “match on word” specified, a filter of “all” will return not only the word “all”, but additional words in which the character string “all” is embedded, such as “allow”, “allocate”, and “mall”.

Sharing of Filters Among Users

Prior to this release, Code Coverage mainframe filters used for identifying “high-risk” code couldn’t be shared between ISPF users. The filters were saved within an ISPF profile for individual reuse, but there was no way to make them available to other Code Coverage users.

With this enhancement, Code Coverage provides a facility that allows filters to be shared among multiple users.

CICS System Flow Reporting

Release 3.1, in conjunction with Xpediter/CICS, provides the ability to print out CICS System Flow information from the standard mainframe Code Coverage reports menu. System name, test ID, and user ID can be used as filters to the report generation process.

This System Flow information can be particularly useful for sites that have inherited unfamiliar, often complex, applications, either from outsourcing or through mergers, and are eager to gain some initial understanding of what’s going on inside them. In such situations, the calling sequence determined at runtime can provide valuable insights.


Xpediter/Code Coverage Maintenance Support

Compuware is committed to actively supporting its current product releases. Up-to-date product release support and retirement information is available on Compuware’s FrontLine Support - Product Currency Tables page.


Software and Hardware Requirements

For further information about IBM System z software and hardware compatibility--specifically regarding IBM's z/OS Recommended Service Upgrade, IBM's Extended Address Volumes, IBM DB2 for z/OS, and z/OS product compatibility--refer to http://frontline.compuware.com/charts/hardware.aspx .

Hardware Platforms

  Mainframe Systems:

-- zEC12, zBC12

-- z196, z114

-- z10-EC/BC

-- z9-EC/BC

-- z900, z990

-- z800, z890

Operating Systems

  IBM z/OS V1.12, 1.13, 2.1

  IBM ISPF for the supported z/OS releases

Languages

  For a list of supported languages, refer to the applicable Xpediter/CICS or Xpediter/TSO and Xpediter/IMS installation guide. Xpediter/Code Coverage does not support the C programming language even if this language is supported by the debugger.

Corequisites

  Compuware Products and Components:

-- Xpediter/CICS 9.3, 9.4, 16.5, 17.2

-- Xpediter/IMS 9.3, 9.4, 16.5, 17.2

-- Xpediter/TSO 9.3, 9.4, 16.5, 17.2

Discontinued Support

This is the last release to support the following:

  OS 390

  z/OS 1.1-1.13

  IBM IMS Transaction and Database Servers V11.1 and 12.1


Technical Notes

There are no technical notes at this time.


Known Issues

The Test Data Optimization (TDO) feature in Xpediter/Code Coverage has been restored for COBOL 5.1 with PTF XVC0070.


Product Documentation

The product installation package does not include the product documentation. The following Xpediter/Code Coverage documentation is available in electronic format on the product documentation site at Compuware’s FrontLine customer support website, http://go.compuware.com .

  Release Notes in HTML format

  The product manuals in PDF format, which may include a PDX index file and associated folder.

Access the Xpediter/Code Coverage documentation on the FrontLine documentation site at go.compuware.com .

PDF and PDX Files

View and print the PDF files with Adobe Reader version 6.0 or more current. Download a free copy of the reader from Adobe’s website, http://www.adobe.com .

Note: With a few minor exceptions, the provided PDF files comply with the requirements of section 508 of the Rehabilitation Act of 1973.

How to Use a PDX File to Search a Compuware Documentation Set

Compuware creates a PDX file for each release of every mainframe product. The file is available in ZIP format on FrontLine, Compuware’s customer support website, along with this README and a folder containing two data files. By pre-cataloging the content of the product’s PDFs, the PDX file allows you to quickly search across the entire documentation set without having to search each PDF individually.

To use the PDX file for a Compuware product:

1. Go to FrontLine (go.compuware.com) and navigate to the Documentation page for the desired product.

2. Download all of the PDF files for that product to the same local directory. (The Compuware Installer PDF is only cataloged in the Enterprise Common Components PDX file.)

3. Download the ZIP containing the product’s index file.

4. Extract the contents of the ZIP, sending it to the same directory as the PDF files. Be sure to select “All files/folders in archive” and “Use folder names.”

5. Double click the product’s PDX file (< product >Index.pdx). A Search dialog box will appear with the index pre-selected.

6. Enter a word or phrase to search for. To optimize your search, select one or more qualifiers such as “Whole words only,” then click Search.

Your search results will appear almost instantly, grouped by document. Each document with results can be expanded to show a list of matches, with each match including a brief sample of the context in which it occurred. Every match is hyperlinked to the specific page in the PDF where it was found, enabling you to quickly locate the information you’re looking for.


Support Resources

Compuware provides a variety of support resources to make it easy for you to find the information you need.

Compuware FrontLine Customer Support Website

You can access online information for Compuware products via our FrontLine customer support website at http://go.compuware.com .

Compuware FrontLine provides access to critical information about your Compuware products. You can review frequently asked questions, read or download documentation, access product fixes, or e-mail your questions or comments. The first time you access Compuware FrontLine, you are required to register and obtain a password. Registration is free.

Contacting Customer Support

Phone

  USA and Canada: 1-800-538-7822 or 1-313-227-5444.

  All other countries: Contact your local Compuware office. Contact information is available at http://go.compuware.com .

Web

You can report issues via the Quick Link Create & View Support Cases on the Compuware FrontLine home page.

Note: Please report all high-priority issues by telephone.

Mail

Compuware Customer Support
Compuware Corporation
One Campus Martius
Detroit, MI 48226-5099

Corporate Website

To access Compuware’s site on the Web, go to http://www.compuware.com .

The Compuware site provides a variety of product and support information.