Adding Compiler Feedback Information to Team Concert z/OS Dependency Builds

Strongback Consulting

In Rational Team Concert’s build functionality, there is capability to show the build compilation report. This is available by a simple checkbox for Java type builds, but in z/OS dependency builds, it requires some additional configuration to get it working property.

A compilaton report can show errors and warnings that occured durring the compile. It is vastly more productive to vizualize them in a consolidated report rather than sifting through translator output logs or, worse, JCL output. Here is what a typical compilation report for z/OS dependency builds looks like.

Note, the Compilation tab. If you double click on any of the warning lines in the Compile Output window, it will navigate you directly to the line in the source member.

The compilation report is dependent upon IBM Developer for z being installed on the same LPAR as the RTC Build Agent (BLZBFA started task).

You will also require these items in your system definitions:

SFELLOAD Data Set Definition

This data set definiton should point to the SFELLOAD dataset where ELAXMGUX load module is located. This module is called during compilation as a program Exit. Shown below is an example. Note the data set name has the high level qualifer of FELE10, which is the default location for IBM zD&T version 12. Consult your systems programmer to confirm the location in your own environment.


Add the Exit param On your Translator

Add the EXIT(ADEXIT(ELAXMGUX)) parameter to each of your compilations. Below is an example for a COBOL compile option.

Add the SFELLOAD to the Tasklib of the Translator

Scroll down to the Data Set Properties section, and under DD concatenations, add your SFELLOAD to the TASKLIB DD (not SYSLIB!).

Add SYSXMLSD and SYSADATA allocations

In the DD allocation section, if allocations for SYSXMLSD and SYSADATA are not already included in the list, add them. SYSXMLSD and SYSADATA must point to data set definitions that represent temporary files on your system.

SYSADATA Allocation

SYSXMLSD Allocation










WSEDSF1-4 with the same characteristics as SYSXMLSD

In addition to the SYSXMLSD dsdef, you also need 4 more sysdefs named WSEDSF1-4 with the same characteristics as SYSXMLSD.  This is in the Knowledge Center documentation for PL1 but not COBOL (although they are required for both).

Once you have these settings, you should now be able to run your dependency build and view compiler output on the build result.

Comments are closed.

Strongback Consulting