7.6 Coordinating the New VOB with Existing VOBs

A typical project involves multiple VOBs. To ensure that they all work together, you must coordinate their type objects: branch types, label types, and so on. For example, the following config spec can be used to create a view that selects the source versions for a previous release:

element * REL_3

For this strategy to succeed, all relevant VOBs must define version label REL3; that is, label type REL3 must exist in each VOB:

• If you are using global types, create the label type with the -global option to mklbtype. The VOB that stores this global type becomes, by definition, an administrative VOB. Users in other VOBs then link to the administrative VOB by creating instances of the predefined hyperlink type AdminVOB that point to the administrative VOB. Thereafter, users in any VOB can create instances of label REL3.

• If you are not using global types, use cptype to copy type objects from one VOB to another.