For an existing view or VOB, the mktag command creates or replaces an entry in the registry. A view or VOB gets one tag when it is created with mkview or mkvob.
In ClearCase, you can use mktag to create additional tags, enabling access from multiple network regions. Each network region needs its own tag for a view or VOB. A single region cannot have multiple tags for the same VOB. (Multiple tags for a view are valid, but not recommended.) However, a single tag can be assigned to multiple regions with multiple mktag commands. For a discussion of network regions, see the IBM Rational ClearCase Administrator's Guide.
By default, creating a view tag activates the view on your host by implicitly performing a startview command. This does not occur if your host is not in the tag's assigned network region or if you use the –nstart option. For a dynamic view, creating the view tag also activates the view. However, creating a VOB tag does not activate the VOB; use mount for this purpose.
This option also enables you to convert private VOBs to public and vice versa, and to change startview behavior. (To change a private VOB to public, you must provide the tag-registry password. To change a public VOB to private, you must be the VOB owner.)
To mark a view tag for export, you must create the tag in the view server host's default region. You cannot use this option when creating view tags in a nondefault region.
In these cases, if you do not include a password, you are prompted for it. The value you specify is checked against the tag registry password; an error occurs if there is no match. For more information, see the Administrator's Guide.
To create a tag for a VOB or view that resides on a supported network attached storage (NAS) device, you must specify the option set, –host –gpath. (NAS devices must be specially configured for use with ClearCase. See the IBM Rational ClearCase Administrator's Guide for details.)
The information you provide is written to the registry exactly as you specify it.
ClearCase. The path name must specify a location on a host where the ClearCase installation is not client-only. For storage intended for snapshot views or VOBs to be accessed only through snapshot views, the path name must be a UNC name only if there is a global path to the server storage location (that is, you have not specified –ngpath).
ClearCase on Windows. For storage intended for dynamic views or VOBs they access, the path name must be a UNC name.
NAS devices providing storage for ClearCase on UNIX, Linux, or Windows. The path name must specify a location on the NAS device that is accessible to all ClearCase hosts in the region.
ClearCase on Windows. The path name must not be within a Windows special share, such as the share that is designated by drive$ and that allows administrators to access the drive over the network.
The UNIX system and Linux examples in this section are written for use in csh. If you use another shell, you may need to use different quoting and escaping conventions.
The Windows examples that include wildcards or quoting are written for use in cleartool interactive mode. If you use cleartool single-command mode, you may need to change the wildcards and quoting to make your command interpreter process the command appropriately.
In cleartool single-command mode, cmd-context represents the UNIX system and Linux shells or Windows command interpreter prompt, followed by the cleartool command. In cleartool interactive mode, cmd-context represents the interactive cleartool prompt.
cmd-context mktag -view -tag view5 ^
-region europe /net/gw/host3/view_store/view5.vws
cmd-context mktag -vob -tag \us_east1 -region europe -public ^
-password tagPword \\earth\vb_store\vob1.vbs
cmd-context mktag -vob -tag \publicvob -replace -public ^
-pass tagPword \\saturn\vobs\private.vbs
cmd-context mktag -view -tag bugfix -replace \
-ncaexported /net/neon/views/bugfix.vws
cmd-context mktag -vob -tag /vobs/dev -replace \
-ncaexported /net/pluto/vobstore/dev.vbs