IPnom Home • Manuals • ClearCase

 Rational ClearCase Commands Reference

ClearCase Stuff:ClearCase LinksClearCase BooksClearCase Commands ReferenceClearCase ForumsClearCase News
Keyword Live Search (10 results max):
 Type in part of a ClearCase command in the search box.
Commands Index:


Changes storage location of derived object data container


ProductCommand type



Invoked by clearmake, omake, or winkin, if necessary, when it winks in a derived object


Note: Never run promote_server manually. It must be invoked only by clearmake or omake. For information about transferring a derived object's data container to VOB storage, see the view_scrubber reference page.

The promote_server program migrates a derived object's data container file from private storage to shared storage. When clearmake or omake winks in a derived object (DO) that was previously unshared, it invokes promote_server to copy the data container file from view-private storage to a VOB storage pool.

Note: clearmake or omake also migrates a DO's configuration record from private storage to shared storage at the same time. This work is performed by clearmake or omake itself, not by promote_server.

The destination storage pool is determined by the DO's pathname. By definition, this pathname is under a VOB tag; that is, the DO is in some VOB directory. The DO storage pool to which the directory element is assigned is the destination of the promotion. (On UNIX systems, some build scripts create multiple hard links, in different directories, to a derived object. In this case, the data container is promoted to the storage pool of only one of the directories.)

clearmake or omake invokes promote_server by making a request to the ClearCase master server, albd_server. promote_server runs as the owner of the view in which the data container to be copied resides (UNIX) or as the user clearcase (Windows), which guarantees read access to the data container.

After promoting a DO, the promote_server remains active for several minutes to ensure that subsequent promotions from the same view are processed with the least overhead. During this time, the promote_server remains associated with the view from which the DO was promoted; if two users try to promote DOs from the same view, at the same time, they share (serially) the same promote_server.



ClearCase Links • ClearCase Books • ClearCase Commands Reference • ClearCase Forums • ClearCase News