Build Information Example

With the PTFs for APAR OA21104 applied, a build information is returned in the build report data set. Just like the normal report mode build, the title page identifies the date and time of the build, as well as the scope and mode used. It also lists the member you specified on the Build panel and the project definition specified on the SCLM Main Menu.

The report lists, in XML format, all members in the scope of the build that would have been built if the build had been performed in "Forced" mode. For each member, the language is listed and each translator within the language definition is shown. For each translator, the options passed to the translator, along with any include dependency DD allocations, are shown.

Figure 1 shows an example of a build information report.

Figure 1. Build Information Report

*******************************************************************************
*******************************************************************************
**                                                                           **
**                                                                           **
**             SOFTWARE CONFIGURATION AND LIBRARY MANAGER (SCLM)             **
**                                                                           **
**                         B U I L D    R E P O R T                          **
**                                                                           **
**                         2007/06/18   16:33:02                             **
**                                                                           **
**                          PROJECT:      ADMIN10                            **
**                          GROUP:        DEV1                               **
**                          TYPE:         COBOL                              **
**                          MEMBER:       RDBKC01                            **
**                          ALTERNATE:    ADMIN10                            **
**                          SCOPE:        NORMAL                             **
**                          MODE:         INFORMATION                        **
**                                                                           **
**                                                                           **
*******************************************************************************
*******************************************************************************

<?xml version="1.0"?>
<build-information>
  <member name="RDBKC01" lang="COBCICD2"
          langdesc="ENTERPRISE COBOL WITH CICS AND DB2">
    <translator name="IGYCRCTL">
      <option-set>
        <option-string>NONUM,LIB,XREF(FULL),MAP,OFFSET,</option-string>
        <option-string>NOOPTIMIZE,CICS(&quot;COBOL3&quot;),SQL</option-string>
      </option-set>
      <data-definition name="SYSLIB">
        <dsn name="ADMIN10.DEV1.COBOL"/>
        <dsn name="ADMIN10.TEST.COBOL"/>
        <dsn name="ADMIN10.PROD.COBOL"/>
        <dsn name="ADMIN10.DEV1.COPYBOOK"/>
        <dsn name="ADMIN10.TEST.COPYBOOK"/>
        <dsn name="ADMIN10.PROD.COPYBOOK"/>
        <dsn name="ADMIN10.DEV1.DCLGEN"/>
        <dsn name="ADMIN10.TEST.DCLGEN"/>
        <dsn name="ADMIN10.PROD.DCLGEN"/>
        <dsn name="CICS.TS31.CICS.SDFHCOB"/>
        <dsn name="CICS.TS31.CICS.SDFHMAC"/>
      </data-definition>
      <data-definition name="DCLGENC">
        <dsn name="ADMIN10.DEV1.DCLGEN"/>
        <dsn name="ADMIN10.TEST.DCLGEN"/>
        <dsn name="ADMIN10.PROD.DCLGEN"/>
      </data-definition>
    </translator>
  </member>
</build-information>

Note that standard XML rules apply to certain special characters, called pre-defined entities. If there are any of the pre-defined entities in the translator options they will be converted to the required XML format name as specified in Table 1.

Table 1. Pre-defined entities
Character value	Pre-defined entity value	Description
<	<	left angle bracket
>	>	right angle bracket
&	&	ampersand
'	'	single quote character
"	"	double quote character

The following table contains a description of the elements and attributes that make up the build information XML document.

Table 2. Description of the Elements and Attributes in the Build information XML
Name	Description
build-information	Root element. There is a single build information element. Sub-elements member Attributes None
member	There is one member element for each member in the scope of the build information report. For example; if build information is requested on an LEC architecture definition, then there will be a member element for each member in the LEC architecture definition. Sub-elements translator Attributes name Name of the member lang SCLM language of the member langdesc SCLM language description
translator	There is one translator element for each translator step in the SCLM language definition. For example; if a COBOL compile has a separate DB2® pre-compile, then there will be a translator element for the DB2 pre-compile and a translator element for the COBOL compile step. Sub-elements option-set data-definition Attributes name Name of the translator invoked. For example, IGYCRCTL for the COBOL compiler
option-set	There is one option-set element for each translator. This will contain a number of option-string elements depending on how many options there are. Sub-elements option-string Attributes None
option-string	There are one or more option-string elements depending on the number of options specified in the translator. This element contains as many options as will fit within an 80 byte record. Sub-elements None Attributes None
data definition	There is one data-definition element for each IOTYPE=I (Include dependency) allocation in the translator. This will contain a number of dsn elements depending on how many data sets are allocated to the specified DD. Sub-elements dsn Attributes name Name of the DD specified in the FLMALLOC macro for an IOTYPE=I allocation. For example; SYSLIB and DCLGEN.
dsn	There is one dsn element for each data set that is allocated as part of the concatenation of DDs for the DDNAME specified in the name attribute of the data-definition element. Sub-elements None Attributes name Data set name