Dimensions enables you to capture build outputs and check them into Dimensions. This functionality is also referred to as a closed-loop build. If you choose to capture build outputs the following actions occur in the final stages of a build after all relevant job steps have been completed:
Dimensions Build captures the build targets defined in the build configuration.
By default, build targets are checked into the Dimensions project from where you initiated the build. You can choose to put the targets in a different project. The default Dimensions upload rules automatically derive the file format and item type of the outputs (see the Process Configuration Guide for details).
The upload rules for MVS build outputs stored in a PDS/E or PDS, such as MERVK.VT.LOAD(SUBB), are defined in terms of the data set low level qualifier, converted to lower case, for example, %load. By default, listing data sets are held per module. The upload rules for generated listings, such as MAL.UT.SUBB.LLISTINGS, are also defined in terms of the data set low level qualifier, converted to lower case, for example, %llisting. Listing data sets can also be placed in libraries
(PDS/E or PDS) for which the upload rules are defined the same as for other build outputs stored in a PDS/E or PDS.
Preservation rules specify whether to preserve each build output as a normal, placeholder, external item revision, or none. See Preservation Rules and Policies for details.
The build outputs are created in Dimensions at the initial lifecycle state and the initial stage, for example, Development.
The Dimensions server creates relationships between every captured target and the source items used to build the target. The server also creates a post-build bill of materials report showing all the components (revisions) that went into the build. This report is stored in Dimensions and any e-mail notifications that have been set up are sent to subscribers.
The Dimensions server relates the captured outputs to the requests that you optionally specified when you initiated the build.
If the build used inputs that are not under the control of Dimensions, this information is stored in the Dimensions repository and in the made-of report. For example, if you are using Openmake the search path includes locations that are not defined as Dimensions build areas.
For details about capturing build outputs and viewing items derived from closed-loop builds see the User's Guide or the online help for the desktop and web clients.