To enable build footprinting you must create a BOM. There are two ways that you can create a BOM:
Use the BOM API from a customer written program called by the build template. This API can be used on all platforms. See the Developer’s Reference for details.
(MVS only) Use the SBEM (Secondary Build Execution Monitor) and in your build template. Add the following line:
//*SBEM TFP DDNAME [(*)] [listing-type-name]
Using TFP instead of the TGT causes the SBEM to generate the required entry in the BOM. For details about using the SBEM see page 250.
There is an example of this technique in Dimensions in:
<Dimensions instance>.TEMPLATE(MDHBLNKC)
Serena does not provide a solution for embedding footprint report names in targets. However, on MVS for standard LOAD modules Serena supplies a program called MDHLLNK0 that enables you to embed footprinting information. For more information see MDHLLNK0.
Use the variable DM_FOOTPRINT_FOLDER in the Dimensions configuration file, dm.cfg, to configure the name of the footprint report and its associated path. You can customize the report name by including special formatting symbols prefixed by a plus '+' sign:
+p: specifies the build node.
+a: specifies the area name (spaces are replaced by an underscore ’_’).
+j: specifies the job number.
+z: a six digit character identifier (MVS only).
Default value: FOOTPRNT/J+z.XML
|
|
|
NOTE The +p,+a, and +j expansions are not suitable for use in MVS projects that use deployment areas as these may generate strings that are not compatible with MVS data set naming standards. |