DSEE Build Unit Specifiers: build_unit_specifier Identifies a buildable component of a system model. Format name[/name...] Description Build_unit_specifier identifies a buildable system component (that is, a system component with either a translate or nil_translation declaration). The build and show builds commands both take the build_unit_specifier argument. (A build unit specifier is also part of the full_build_name argument. Type help full_build_name to get more information about full build names.) Usually, a system component's name suffices as its build unit specifier. For example, DSEE> build beta.pas directs the configuration manager to build system component beta.pas. Likewise, DSEE> show builds t2.pas shows the headers of all build maps associated with the system component t2.pas. The system model language allows you to declare two or more system components with the same name, as long as they do not occur at the same level in the system model's block hierarchy. However, a build unit specifier must identify, unambiguously, one unique system component. If you're building a system component whose name is not unique, its build unit specifier must be a pathname. A build unit specifier that is a pathname is like a regular pathname, but instead of describing the path from a directory to a file, it describes the path from a superior level in the system model to a component's declaration. This kind of build unit specifier starts with the highest-level uniquely-named system component that "contains" the desired component, and continues down the system model hierarchy without skipping any intermediate levels until it reaches the declaration for the subcomponent. For example, DSEE> build alpha/open.pas directs the configuration manager to build alpha/open.pas (the system component open.pas that is a subcomponent of system component alpha). Similarly, DSEE> build aggregate_a/alpha/open.pas directs the configuration manager to build the component open.pas that is part of alpha, that, in turn, is part of aggregate_a. build_unit_specifier_list Identifies one or more build unit specifiers, or a file containing the names of one or more build unit specifiers. Format build_unit_specifier [build_unit_specifier ...] *pathname Description The create release and edit release commands take the build_unit_specifier_list argument in their -export clauses. The build unit specifier list is either a list of build unit specifiers or the name of a file containing a list of built unit specifiers. Precede a build unit specifier list filename with an asterisk. For example, type DSEE> create release /rls/b2 -from mysys!10-Apr-1985.10:22:37 -export *rls/rls_l to release the items listed in the file rls_list. wildcard_build_unit_specifier Identifies one or more buildable system model components. Format [pathname/]wildcard_specification Description Wildcard_build_unit_specifier identifies a set of buildable system components. A wildcard build unit specifier can be a simple wildcard, such as beta?*.pas, or a system model hierarchy pathname whose last component includes a wildcard, such as backend/?*.pas. If the wildcard build unit specifier is a simple wildcard, all buildable system components are possible matches. For example, DSEE> show builds beta?*.pas shows the build map headers of all system components whose names match the wildcard beta?*.pas (beta.pas, beta_1.pas, and so on). If the wildcard build unit specifier is a system model hierarchy pathname whose last component includes a wildcard, only the direct subcomponents of the component named by the path are possible matches. For example, DSEE> show builds backend/?* shows the build map headers of all direct subcomponents of backend. So, for example, the configuration manager would display the build map headers of backend/open.pas and backend/aggregate_alpha, but not that of backend/aggregate_alpha/alpha.pas.