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