Source Support


Accessing the BMC AMI DevX Source Support Dashboard

Select the BMC AMI DevX Source Support link from the zAdviser Enterprise On-Prem Home Page to go directly to this dashboard.

image-2023-3-22_21-21-52.png

About  BMC AMI DevX Source Support 

 BMC AMI DevX Source Support allows a user to view a program's source code with line numbers when using the following products:

  • Abend-AID
  • Abend-AID for CICS
  • Code Debug CICS
  • Code Debug/TSO include
  • Code Debug/Eclipse (Topaz) 
  • Strobe

There are two methods for creating the source support:

  • Pre-Processor Source Support
  • Post-Processor Source Support

Pre-Processor Source Support

The Pre-Processor will invoke the appropriate compiler and create the source listing dataset for use with the identified products.

Preprocessor Steps

  1. Determines the proper compiler options required to process the listing file.
  2. Automatically invokes the compiler or assembler to compile or assemble your source program.
  3. Writes the listing to the DDIO file.

Pre-Processor Benefits

  • Better Handling of Compile Errors
    By using the preprocessor, you can avoid the potential problems of processing a listing with compiler errors. The preprocessor, in conjunction with the CONDDDIO parameter, internally checks the return code from the compiler and does not write a DDIO listing that contains errors. For example, if you set the CONDDDIO parameter to 8, the preprocessor will write the compiler listing to the DDIO file unless the compiler return code exceeds 8. The preprocessor can process compiler errors more effectively than the postprocessor can.
  • Capturing of suppressed source code
    When the parameter COPY SUPPRESS (example for COBOL) is used, sections of source code can be suppressed from the compiler listing. The pre-processor captures this information from SYSIN and SYSLIB.
  • Automated Compiler Options
    The post-processor requires that certain compiler options be specified in order to process all needed sections of the compiler listing, when processing as a single source code unit, the pre-processor can automatically pass the required options to the compiler.
  • Simplified JCL
    While the postprocessor requires that you add a step after the compile step, the Pre-Processor requires only that minor modifications be made to your existing compile step.

Post-Processor Source Support

The Post-Processor is invoked as a single step. It reads one or more listings from a compiler and creates the source listing required by the products. Information is gathered from the source listing(s), XREF, data maps, and object code sections of the listing(s). This information is stored in a DDIO file member(s) and is used by various BMC AMI DevX companion products.

While the preprocessor is the preferred method of loading the compiled listing to the DDIO, there are situations that require the use of the postprocessor as a viable alternative. This is commonly found in production environments where the listings may be archived. Note that these are usually the default options at many shops.

  • If the programs contain suppressed source code, certain additional control statements must be added to the language processor.
  • If the programs are compiled with the COBOL compiler option OFFSET as well as the COBOL compiler option OPT(imize), certain additional control statements must be added to the language processor.

Post-processor Benefits

  • Post-processing provides an exact match of compiled output listings with the executable load module. This benefit is especially important in production environments where time is critical and where the production program was compiled with a version of the compiler that is no longer available.
  • Postprocessing eliminates the risk of copybook or source code changes prior to recompiling the code since the listing reflects the code that is being executed.
  • The processor resources utilized to process source listings are significantly reduced compared to recompiling the source code, and the language processor can automatically run on the specialty processor (zIIP) when available.

For more information about Source Support, see BMC Compuware Shared Services User Reference Guide.

BMC Compuware Source Support Visualizations

Pre-Processor Source Listing Reports Generated

Identifies the total number of Pre-Processor Source Support requests that were executed during the period.

Pre-Processor Source Listing Reports Generated.PNG

Post-Processor Source Listing Reports Generated

Identifies the total number of Post-Processor Source Support requests that were executed during the period.

Post-Processor Source Listing Reports Generated.PNG

Source Listing Reports Generated Trend

The Source Listing Reports Generated Trend visualization shows a trend of the number of Source Listing Requests differentiated by Pre-Processor and Post-Processor Support requests as a daily count. The 7-day Moving Average represents both requests.

Source Listing Reports Generated Trend.PNG

Source Listing Reports Generated by Type

The Source Listing Reports Generated by Type visualization provides a pie chart showing the count and percentage of BMC AMI DevX Source Support compiles broken out by Pre-Processor and Post-Processor requests as defined above.

Warning

Tip

Clicking on either Pre-Processor or Post-Processor enables a filter that will show only that type of activity in the Dashboard.

Source Listing Reports Generated by Type.PNG

Embedded Source Support Option During Report Generate

The Embedded Source Support Option During Report Generate visualization provides a pie chart showing the count and percentage of BMC AMI DevX Source Support compiles with the Embedded Source Support option by the option represented by Embedded or Off.

Warning

Tip

Embedded Source Support appends the Source Support to the Load module that is executed. The Source listing data is not loaded with the executable code. Using this feature can simplify the use of the tools that exploit it. This requires additional space in the PDS/E to support the embedded source code depending on the size of the programs.

Embedded Source Support Option During Report Generate.PNG

Source Listing Reports Generated by Language

The Source Listing Reports Generated by Language visualization a data table with the request that are being generated by language and version. Clicking on the Formatted button at the bottom will export and download the data to CSV file.

Warning

Tip

Placing your mouse over a language and version, will provide a + and - in a magnifying glass. Clicking the + will show only activity associated with that line item. If the goal is to what programs are being worked with that at COBOL v4.2 or older, setting filters both positive filters and negative filters will allow the analyst to see what users and programs are being used with those versions.

Source Listing Reports Generated by Language.PNG

Source Listing Reports Generated by Program and Language

The Source Listing Reports Generated by Program and Language visualization provides a table that details the programs source support is being generated for and language version of the program.

Warning

Tip

Setting a filter on a specific Program name, shows only the activity associated with that program.

Source Listing Reports Generated by Program and Language.PNG

User Count by Language

The User Count by Language visualization provides a pie chart with a count of users who are generation requests for source support in the different languages.

User Count by Language.PNG

Users Generating Source Listing Reports

The Users Generating Source Listing Reports visualization provides a table of users who are creating the most Source Support Requests.

Warning

Tip

Clicking on a user name sets a filter that allows the analyst to understand what programs and whether they are using Pre or Post Processing for their source support needs.

Users Generating Source Listing Reports.PNG

Source Listing Reports Generated by LPAR

The Source Listing Reports Generated by LPAR visualization provides a pie chart detailing which LPARs that Source Listing Reports are being generated on.

Warning

Tip

Clicking on a specific LPAR section of the Pie Chart will set a filter for that LPAR. This will allow you to understand who and what programs are being processed on that system.

Source Listing Reports Generated by LPAR.PNG


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC AMI zAdviser Enterprise On-Prem 26.04.00