25.8 Managing VOB and View Registry Entries

ClearCase creates VOB-tag and VOB object registry entries when you create a VOB. It creates view-tag and view object registry entries when you create a view. You can use the ClearCase Registry node of the ClearCase Administration Console or various cleartool subcommands to inspect, create, and repair registry entries.

Viewing VOB and View Registry Entries

Use the VOB Objects and View Objects subnodes of the ClearCase Registry node in the ClearCase Administration Console to inspect VOB and view object entries:

1. Start the ClearCase Administration Console.

2. Navigate to the VOB Objects or View Objects subnode of the ClearCase Registry node.

3. Select a VOB object or view object in the details pane.

4. Click Action > Properties.

Use the VOB Tags and View Tags subnodes of a region in the ClearCase Registry node in the ClearCase Administration Console to inspect VOB-tag and view-tag entries:

1. Start the ClearCase Administration Console.

2. Navigate to the VOB Tags or View Tags subnode of a region in the ClearCase Registry node.

3. Select a VOB-tag or view-tag in the details pane.

4. Click Action > Properties.

You can also use lsvob or lsview with the -long option to report key registry information. If you cannot see a VOB with lsvob or a view with lsview, then no tag for the view is registered in the current network region (or for the region specified in the command). For a VOB or view with a registered tag, the output from lsvob -long and lsview -long includes this information:

• The VOB-tag or view-tag

• The host name for the host on which the storage directory resides

• The host-local access pathname (from the vob_object or view_object file), which the relevant VOB or view server uses to access the storage directory

• The global pathname (from the vob_tag or view_tag file), which is used to resolve references to the newly created VOB

For example:

cleartool lsvob -long
.
.
Tag: /vobs/src
Global path: /net/venus/vobstore/src.vbs
Server host: venus
.
.
Vob server access path: /vobstore/src.vbs
.
.

cleartool lsview -long
.
.
Tag: main
Global path: /net/venus/viewstore/main.vws
Server host: venus
.
.
View server access path: /viewstore/main.vws
.
.

If the global and server access paths are identical or if they don't look right to you, then you may anticipate problem reports regarding access to the VOB or view.

Creating VOB and View Registry Entries

The mkvob and mkview commands and the GUI tools that create VOBs and views create both the object and tag registry entries necessary for ClearCase client access. (There is one exception: if you create a VOB with a public tag, but the tag password fails, the VOB is created without the tag. You must create the tag in a separate operation with mktag.) mkvob and mkview output includes this information:

• The host-local access pathname (from the vob_object or view_object file)

• The global pathname (from the vob_tag or view_tag file)

Sample mkvob output:

.
.
Host-local path: venus:/vobstore/src.vbs
Global path: /net/venus/vobstore/src.vbs
.
.

Sample mkview output:

.
.
Host-local path: venus:/viewstore/main.vws
Global path: /net/venus/viewstore/main.vws
.
.

Creating VOB-Tags and View-Tags

Use the ClearCase Administration Console or mktag to add or replace tag entries for existing VOBs and views. These are two common uses:

• Creating additional VOB-tags and view-tags to support multiple network regions

• Converting a private VOB to a public VOB

To change a tag's name or its assigned region, use the ClearCase Administration Console to remove the tag and create a new one, or use rmtag and then mktag, not mktag -replace. See the mktag and rmtag reference pages for details on tag creation and removal.

To change the assigned network region for a tag or to copy a tag in another region, you can drag the tag from one region to another using the Regions subnode of the ClearCase Registry node in the ClearCase Administration Console. If you change a tag's region, be sure that the global path is valid in the new region.

Figure 33 shows the cleartool commands that affect registry files.

Figure 33 cleartool Commands and the ClearCase Storage Registry