Nearly every operation that modifies the VOB creates an event record in the VOB database. For example, when you create a new element, attach a version label, or lock the VOB, an event record marks the change.
Event records are attached to specific objects in VOB databases. Thus, each object (including the VOB object itself) accumulates a chronological event history, which you can display with the lshistory command.
In addition, you can do the following:
An event record stores information for various operations:
Full name information is written into an event record created on a ClearCase client on UNIX, Linux and Windows. On Windows, you need to set the full_name field on a domain controller. You can do this in two ways.
net user user-name /fullname:″name-string″ /domain
Where name-string is the name you want written into an event record. Here is an example:C:\> net user tdawson /fullname:"Terry Dawson" /domain
Terry Dawson (Senior Software Engineer)
ClearCase will extract ″Terry Dawson″ to use as the name in an event record.HKEY_LOCAL_MACHINE\SOFTWARE\Atria\ClearCase\CurrentVersion\
DisableGecos
The following kinds of VOB database objects have event histories, which you can display with lshistory:
Each time an object from any of these categories is created, it begins its own event history with a creation event. (Derived objects are an exception; ClearCase stores a DO's creation time in its config record, not in an event record.) As time passes, some objects, VOBs and elements, in particular, can accumulate lengthy event histories.
Do not confuse type objects (created with mkattype, mkbrtype, mkeltype, mkhltype, mklbtype, and mktrtype) with the instances of those types (created with mkattr, mkbranch, mkelem, mkhlink, mklabel, and mktrigger). The type objects are VOB-database objects, with their own event histories. Individual branches, elements, and hyperlinks are also VOB-database objects. However, individual attributes, labels, and triggers are not VOB-database objects and, therefore, do not have their own event histories. Their create and delete events (mkattr/rmattr, mklabel/rmlabel, and mktrigger/rmtrigger) are recorded on the objects to which these metadata items are attached.
The following kinds of operations cause event records to be written to the VOB database:
If UCM is in use, the following kinds of operations cause event records to be written to the UCM Project VOB (PVOB) database.
Table 1 lists event-causing base ClearCase operations as you may see them in lshistory output that has been formatted with the –fmt option's %o (operation) specifier. Note that most operations correspond exactly to cleartool subcommands.
Each of the following superoperations represents a group of the event-causing operations listed in Table 1 and Table 2. For information about how to use the following keywords to write triggers for groups of operations, see mktrtype.
Table 1 omits the triggerable operations uncheckout and chevent; as these operations do not cause event records to be stored in the VOB database.
The set of ClearCase commands in Table 1 matches almost exactly the set of commands that accept user comments as input. (reformatvob, which takes no comment, is the only exception.) When you supply comments to a ClearCase command, your comment becomes part of an event record.
Some cleartool commands create a comment even if you do not provide one. These generated comments describe the operation in general terms, such as “modify metadata” or “create directory element.” User comments, if any, are appended to generated comments. For a complete description of comment-related command options and comment processing, see the comments reference page.