7.5 Windows Tags for UNIX VOBs with Symbolically Linked Storagecontents@cc_inter.hlp">

NOTE: This section applies only if you are using an NFS Client product to access VOBs with symbolically linked storage pools; if you are using a supported SMB server product, you need not follow the instructions in this section.

If a UNIX VOB includes one or more symbolically linked storage pools, the VOB requires special handling when you register it in a Windows network region. Before you do so, check for linked storage pools. If you discover you have already registered a VOB without accounting for its linked storage pools, see Mapping Storage Pools for an Existing VOB-Tag.

To check a VOB for linked storage pools, move to a UNIX computer and type a command similar to this one:

cleartool lspool -long -invob /vobs/libvob
...
pool "libvob"
18-Jun-97.17:00:06 by VobAdmin(VobAdmin.sys@starfield)
kind: source pool
pool storage link target pathname "/net/gamma/pools/libvob.1"
pool storage global pathname "/net/io/vb_store/myvob/s/sdft"
...

If the output includes one or more pool storage link ... lines, follow this procedure when you create the VOB-tag with the Region Synchronizer:

  1. Select the VOB-tag, and click Import.

  2. In the Create VOB Tag dialog box, click Show Mount Options.

  3. Under NT-Only Options, in the Split Pool Map box, supply a one-line text string that specifies all remote storage pools. For example, the following line (which is broken, illegally, so you can read it) defines three remote pools, separated by vertical bars:

  4. s\sdft\=\\gamma\pools\s\libvob.1\
    |c\cdft\=\\gamma\pools\c\libvob.1\
    |d\ddft\=\\gamma\pools\d\libvob.1\

    In this example, the VOB storage directory is on io but includes symbolic links to source, cleartext, and derived object pools on gamma.

    NOTE: Pathnames are specified with UNC names, a backslash (\) terminates each path name, and vertical bars (|) separate individual pool mappings.

Mapping Storage Pools for an Existing VOB-Tagcontents@cc_inter.hlp">

If you discover that you have already registered a VOB without accounting for its linked storage pools, use the ClearCase Administration Console on a ClearCase host running Windows to change properties of the tag:

  1. Navigate to one of the following nodes:

  2. Select a VOB-tag in the details pane.

  3. Click Action > Properties. This command opens a dialog box in which you can edit properties of the tag if you are a member of the ClearCase administrators group.

  4. In the dialog box, click the Mount Options tab. Enter a pool map string in the Split Pool Map box using the syntax described in Windows Tags for UNIX VOBs with Symbolically Linked Storage.

You can also delete the VOB-tag with cleartool rmtag and re-create it with the Region Synchronizer.

Alternately, you can re-create the VOB-tag with mktag -replace. A sample mktag command follows:

cleartool mktag -vob -tag \libvob -region dev_nt -replace ^
More? -options poolmap=s\sdft\=\\gamma\pools\s\libvob.1\ ^
More? ^|c\cdft\=\\gamma\pools\c\libvob.1\ ^
More? ^|d\ddft\=\\gamma\pools\d\libvob.1\ ^
More? -host io ^
More? -hpath /usr1/vb_store/libvob.vbs ^
More? -gpath \\io\usr1\vb_store\libvob.vbs ^
More? \\io\usr1\vb_store\libvob.vbs

This command illustrates several important rules to follow when composing the command line:

Here is formal syntax for each pool specification in a poolmap mount option to cleartool mktag:

pool-spec := symlink-source\=symlink-target\

symlink-source

The symbolic link to the remote pool, relative to the VOB storage directory.
symlink-target

The full pathname, in UNC format, of the linked pool. The pool must reside somewhere in a UNIX directory subtree that has been mounted on the local Windows computer using an NFS product. The path name must be valid on all computers in the Windows network region that access the VOB.