rh._.exports({"0":[[" ","Using Item Formats to Control Build Rules"]],"1":[[" ","Using \n Item Formats to Control Build Rules"," ","When you add a build source to a build \n configuration you can specify a build type item format. This enables you \n to add an additional level of granularity and subdivide a large group \n of sources with the same extension or item type into smaller subsets based \n on their unique item format. Wildcards are then scoped using a name match \n and the build type item format."," ","For example, COBOL source code can be \n BATCH, CICS, DB2, IMS, or a combination of multiples. They all have a \n .COBOL extension and are the same item type. However, if you define an \n item format for each one, you can specify a unique build type item format \n when adding build sources. For example, you could have the following COBOL \n build type item formats:"," ","COBOL_CICS"," ","COBOL_DBS"," ","If you specify a build type item format, \n the source is scoped by both the item type (e.g., COBOL(*) and the build \n type item format (e.g., COBOL_CICS)."," ","For details about specifying Dimensions \n item formats, see the ","data \n formats and MIME types information"," in the Administration Console \n online help."]],"id":"189"})