rh._.exports({"0":[[" ","Modifying a Transition Script"]],"1":[[" ","Modifying \n a Transition Script"," ","The following procedure applies to transition \n scripts."," ","To modify a transition script:"," ","In \n\t the Build Administration Console, click the Build Management tab."," ","Check \n\t out the build configuration containing the target whose transition \n\t script you wish to modify."," ","In \n\t the navigation tree, Select the target. The Transition Details section \n\t appears in the content pane."," ","Click \n\t the pencil icon next to the Transition Details title. The Script page \n\t of the Edit Target Wizard appears."," ","For \n\t ","Build Order"," enter a numerical value that \n\t specifies the order in which the transition is built."," ","A value of 0 indicates \n\t\t no order. "," ","Transitions are ordered \n\t\t in the BRD (Build Request Definition) file from 1 to n regardless \n\t\t of where they appear in the tree in Dimensions Build. For example, \n\t\t all transitions with a value of 1 is built before those with a \n\t\t value of 2."," ","This functionality allows \n\t\t you to manually set the order of build steps for unrelated items \n\t\t that Dimensions Build cannot order automatically."," ","The build order of a nested \n\t\t transition cannot be higher than its parent. For example, assume \n\t\t that you have the transition COBOL(*) to OBJECT(*) to LOAD(*). \n\t\t OBJECT(*) can not have a build order of 2 if LOAD(*) has a build \n\t\t order of 1 as it does not make sense to build the LOAD before \n\t\t the OBJECT."," ","Select \n\t the ","Expand Wildcards"," checkbox to:"," ","Expand all the wildcard \n\t\t inputs and outputs for this transition at build time."," ","Create an instance of the \n\t\t transition for each item that matches the wildcard."," ","For more details see ","Support for Wildcards in Build Configurations","."," ","NOTE  "," ","The default state of this \n\t\t checkbox is determined by the platform of the build configuration. \n\t\t For an MVS platform the default is ’expand’ (checked). For all \n\t\t other platforms, the default is ’no expand’ (not checked)."," ","If you have multiple targets \n\t\t in a build configuration you can use both settings (expand and \n\t\t not expand)."," ","If \n\t you want to select a different build tool, use the pull down list \n\t to make a new selection for that field."," ","To \n\t modify the main part of the script, select one of the following four \n\t choices:"," ","input script content manually"," ","If you select this choice, enter \n\t or modify the script in the ","Script Content"," text \n\t box. Select the Word Wrap checkbox if you want to have the text wrap."," ","use a Dimensions-controlled \n\t\t file as a script"," ","If you select this choice, enter \n\t or modify the location of the file, or click ","Browse"," \n\t to browse for it."," ","NOTE  ","If \n\t you select a Dimensions-controlled file as a script, be aware that \n\t the file is pushed to the build area if you are using a work area. \n\t If you are using a deployment area, Dimensions Build assumes that \n\t the script has already been deployed to that area."," ","use a file in the build \n\t\t area as a script"," ","If you select this choice, enter \n\t or modify the location of the file, or click ","Browse"," \n\t to browse for it."," ","use the build configuration \n\t\t main script"," ","If you select this choice, you need \n\t not enter any other information, as ","Dimensions CM"," knows \n\t where to find the main script."," ","If \n\t you added or selected a new script, and need to delete an existing \n\t script, do so now."," ","Click \n\t Finish to accept the changes."," ","Check \n\t in the modified build configuration by clicking the Check In icon."]],"id":"444"})