The footprint report is created at the end of each build. The report has environmental information for the whole build, followed by detailed explosion information about each fully footprinted target.
The format of the footprinting report is as follows:
<SerenaExecutableFootprint>
<Workset>prod:proj</Workset>
<BuildConfig>
<ConfigName>ccccc</ConfigName>
<ConfigDescription>ddddddd</ConfigDescription>
</BuildConfig>
<Environment>
<Node>lllllll</Node>
<Directory>stem</Directory>
<Area>area name</Area>
<DimensionsUser>dimuser</DimensionsUser>
<RemoteUser>platformuser</RemoteUser>
<SubmitData>job(Jnnnnnn)</SubmitData>
<Created>dd-mmm-yy</Created>
</Environment>
<Module>
:
:
</Module>
</SerenaExecutableFootprint>
Where:
prod:proj is the name of the product and project from where the build was run.
ccccc is the name of the build configuration that was used to build the target.
dddddd is the description of the configuration.
lllllll is the MOVS logical node name. For more information, look at the result of building code with the supplied templates.
stem is a series of MVS qualifiers not including the final type (as used when specifying an area).
area name is the name of the area where the build was performed.
dimuser is the name of the Dimensions user who ran the build.
platformuser is the user ID used for the build on the platform (often the area user ID).
job is the number of the job that was submitted.
dd-mmm-yy is the date the job was run.
The <Module> section is included once for each fully-footprinted program object and has the following format:
<Module>
<Name>LOAD/module.LOAD;v</Name>
<ItemSpec>product:Item spec.A-EXE;v</ItemSpec>
<LibraryFileName>module name.load/v</LibraryFileName>
<Dep>
:
:
</Dep>
:
:
</Module>
Each <Dep> section has the following contents:
<Dep>
<Name>type/wsname.type;v/Name>
<ItemSpec>prod:itemspec.A-SRC;v</ItemSpec>
<LibraryFileName>name In ItemLibrary/v</LibraryFileName>
</Dep>