Benefits and overview

BMC Compuware products provide their maximum benefit when the products can associate collected information with the affected programs. This paper describes best practices to ensure your programming staff gets the most benefit from the BMC Compuware programs at all stages of the application lifecycle; it is intended as a supplement to the Compuware Shared Services User Reference.

This process ensures that the Compuware human-readable symbolic file is available at every stage of development and production. This file is often referred to as the BMC Compuware compiler listing and it is stored in a Compuware proprietary VSAM file often referred to as a DDIO; these are also known as source DB files managed under SHRDIR directories.

When you follow the naming standards described in this document, BMC Compuware product users will automatically gain all the benefits of source support with no additional configuration. BMC Compuware products will locate the cataloged source support repository based on the LOADLIB where the program was loaded from.

The following BMC Compuware tools make use of this BMC Compuware compiler listing¹:

• Xpediter – to interactively analyze and debug program code
• Xpediter Code Coverage – to verify that code has been executed in a test
• BMC Compuware Program Analyzer – to instantly draw a chart of program logic and analyze code
• Strobe and iStrobe – to show the line of code where resources were consumed
• Abend-AID – to show the last statement executed and format program storage

Implementing a strategy whereby a BMC Compuware listing is always available is a fairly straightforward process that can mirror your management of source code and executable LOADLIB members. When you move either the object code or the linked module along, if you move the corresponding BMC Compuware listing(s) in parallel, you will always have a source listing available for BMC Compuware tools.

The following figure shows a typical Source Code Management (SCM) promotion process, linking source to loadlib member:

Simple SCM promotion process

When you compile a program, you would save the listing in the repository (unless you are using Embedded Source Support, ESS). When you copy, move or recreate (via a recompile) the LOADLIB member, for example, from test to QA, you would also copy, move or recreate the BMC Compuware listing member. The following figure shows these changes, where the compile listing is contained in Compuware Source Databases (DDIO) attached to Shared Directories (SHRDIR).

BMC Compuware’s ISPW can be configured to treat the DDIO listing as one of the “parts” that are created in the program generate process.

SCM Promotion include BMC Compuware listing

In this configuration, you would create a source listing repository corresponding to each of your LOADLIBS.

If you have composite load modules comprised of multiple compile units, you will need to correlate all the compile listings that make up the LOADLIB member. You would still create and maintain a single source listing repository corresponding to each of your LOADLIBS.

For COBOL releases starting with release 5 and above, you have the option of embedding the listing into the loadlib member, without using a Source Listing Repository (aka ddio file). This is called Embedded Source Support, ESS. For more technical details regarding ESS, see Appendix H.

The following figure Illustrates Source Support with ESS.

SCM Promotion with Embedded Source Support