Prototype for data items stored in a VOB
ClearCase (data structure), Attache (data structure)
A type object is a prototype for one or more data items stored in a VOB database. A user creates the data items by entering commands that create instances of the type object.
For example, to attach the version label BASELEVEL_4.2 to the current versions of a set of source files:
NOTE: The phrase "type object" is sometimes shortened to "type" in ClearCase documentation.
Creating an instance of a type object is not a copy operation. Rather, the instance is a reference to the type object. In the example above, attaching version label BASELEVEL_4.2 to a particular version does not make a copy of the BASELEVEL_4.2 type object. Instead, it establishes a connection between the version object and the label type object.
This scheme makes it easy to administer type objects and their instances. For example, renaming the label type object from BASELEVEL_4.2 to BL4.2 renames all its existing instances.
NOTE: Creating an instance does not make a copy of the type object, but in certain cases it does create a new object. For example, the mkbranch command creates a new branch object and creates a reference connecting the new branch object to an existing branch type object. See PREDEFINED AND USER-DEFINED TYPE OBJECTS for information on which types are associated with objects.
To support different kinds of data items (version labels, attributes, branches, hyperlinks, and so on), there are different kinds of type objects:
The mnemonics listed above are useful as object-selector prefixes in ClearCase product family commands. By default, many commands consider an unprefixed name to be a reference to a file system object, typically a version of an element:
cmd-context describe hoople
(describe the file named `hoople' in the current working directory)
cmd-context describe brtype:hoople
(describe the branch type object named `hoople')
Each VOB is created with a set of predefined type objects. Users can create additional type objects.
file_system_object (internal only; cannot be used in a mkelem command)
directory
file
binary_delta_file
compressed_file
text_file
compressed_text_file
CHECKEDOUT
LATEST
HlinkFromText
HlinkToText
AdminVOB
GlobalDefinition
Merge
RelocationVOB
Each VOB has its own set of type objects, for use in creating instances of the types in that particular VOB. For example, you can attach RLS7.0 version labels within a particular VOB only if label type RLS7.0 already exists in that VOB. Exception: The global type object facility creates type objects on demand by copying them from a networwide repository. See GLOBAL TYPES AND ADMINISTRATIVE VOBS for details.
You can use the global type facility to effectively increase the scope of a type object from a single VOB to a group of VOBs-perhaps all the VOBs in your local area network. You can create any number of global type objects in one or more central administrative VOBs.
For more information about using global types, see Administering ClearCase.
The following commands operate on type objects. For more information about the commands, see ClearCase Reference Manual. For more information about how these commands work with global types, see Administering ClearCase.
| Purpose | Commands |
|---|---|
Type object creation | |
Instance creation | mkactivity, mkattr, mkbranch, mkelem, mkhlink, mklabel, mktrigger |
Renaming | |
Copying | |
Deleting | |
Describing/listing | |
Lock/unlock |
describe, mk**type, rename, rmtype
|
Feedback on the documentation in this site? We welcome any comments!
Copyright © 1999 by Rational Software Corporation. All rights reserved. |