Public and private VOBs

To provide control over how a VOB is mounted, each VOB tag is designated as public or private when it is created.

VOBs themselves are neither public nor private. The distinction rests entirely in the tag. The public/private status of a VOB tag is important only to dynamic views, which can access only those VOBs that are mounted. Snapshot and Web views can access any VOB that has a tag, regardless of whether it is mounted.

Note: Any user can mount any VOB, public or private. The private designation means only that a VOB is not mounted by a cleartool mount –all command and must be mounted explicitly by name.
Public VOB tags are treated somewhat differently on Windows® than they are on Linux and the UNIX system:
  • On computers running Linux or the UNIX system, all public VOBs are mounted as a group when DevOps Code ClearCase® starts. To defeat this behavior, use the noauto mount option at VOB creation time (see mkvob –options).
  • On Windows computers, all public VOBs are mounted as a group when you issue the following command:

    cleartool mount –all

    If you use the –persistent option to cleartool mount, the specified VOBs are mounted each time you log on. To force all public VOBs to be mounted in this way, use the following command:

    cleartool mount –all –persistent

    You can also arrange to have a VOB mounted when you log on by selecting the Reconnect at Logon check box in the Mount window when you first mount the VOB from the DevOps Code ClearCase pop-up menu.
Note: On a client that hosts one or more dynamic UCM views, all the UCM project's VOBs are mounted when the view starts.