Soft - is your software and documentation
The mkvob command
creates a new versioned object base,
or VOB, as follows:
1. Creates a VOB storage directory at a specified path or in a VOB server storage location created with mkstgloc.
2. Creates a VOB tag with which the VOB is accessed by users.
3. Places entries in the network's VOB registries; use the lsvob command to list registered VOBs.
4. Starts a VOB server process on the named host.
5. A VOB storage directory is the root of a directory tree whose principal contents are a VOB database and a set of storage pools. See the mkstgloc reference page for details.
B. Access permissions in considering access permissions, it is important to distinguish these two top-level directories: VOB storage directory. The standard directory created by this command, which is at the top level of a server storage location for VOBs. VOB root directory. The ClearCase or ClearCase LT directory element accessed at the VOB tag. ClearCase and ClearCase LT implement their own access scheme that goes beyond the standard operating system facilities. These settings control access to many operations involving the VOB; they can be changed with the protectvob command.Important: Do not use operating system permission-setting utilities on a VOB storage directory. This creates inconsistencies and causes confusion. See also the protect reference page (this command affects access to individual elements and shared derived objects) and the IBM Rational ClearCase Administrator's Guide.
C. VOB directory elements mkvob creates the following directory elements in a VOB: VOB root directory. A mkdir command is implicitly executed to create a directory element (the VOB root directory) in the new VOB. Activating a VOB makes its root directory accessible at the path name specified by the VOB tag. lost+found directory. In ClearCase, mkvob also creates a special directory element, lost+found, as a subdirectory of the VOB root directory. In this directory are placed elements that are no longer entered in any versioned directory. Default storage pools. Each VOB storage directory is created with default storage pool subdirectories: sdft Default source storage pool cdft Default cleartext storage pool ddft Default derived object storage pool (ClearCase dynamic views)
D. ClearCase dynamic views: Activating the VOB. A VOB cannot be used for development work in a dynamic view until it is activated with the cleartool mount command. This causes the VOB's storage directory to be mounted on the host at the VOB tag location, as a file system of type MVFS. See the mount reference page for details.
E. UNIX VOBs
When you create a VOB on a UNIX system, you become its VOB owner and your groups become its group list. These settings control access to many operations involving the VOB; they can be changed with the protectvob command. Your operating system-level UID and GID are assigned to the VOB storage and the default storage pools. The mode of the VOB storage directory is set according to your current umask setting. This affects which users, and which views, can access the VOB. The modes of storage pool directories are set to 755, regardless of your current umask setting. The mode of the VOB root directory, by contrast, is derived from your current umask setting. The mode can changed subsequently with the protect command. Note that the w permission on this directory (as on any directory element) affects only the creation of view-private objects; changes to the VOB itself are controlled by ClearCase or ClearCase LT permissions, not those at the operating system level.
When you create a VOB on a Windows system, you become its VOB owner and your primary group becomes the VOB's assigned group. These settings control access to many operations involving the VOB; they can be changed with the protectvob command. Your operating system-level user name and the name of the ClearCase administrators group are assigned to the VOB storage and the default storage pools. All users can read and search the storage pools, but only the VOB owner and ClearCase or ClearCase LT server processes can modify them. Interop text mode support
By default, VOBs are created with interop text mode support enabled. In this mode, the VOB database keeps track of the number of lines in all versions of each text file. This mode is required to support access to the VOB by interop text mode views (see the mkview reference page). To change the state of a VOB's interop text mode support, use the msdostext_mode utility. For more information, see the IBM Rational ClearCase Administrator's Guide.
F. Creates one or more event records, with commenting controlled by your .clearcase_profile file (default: –cqe). See the comments reference page.
G. ClearCase: Regional tags. mkvob creates exactly one VOB tag for the newly created VOB. This tag applies to the local host's network region by default. To make additional VOB tags for other regions, use the mktag command. In general, the VOB tags for a given VOB should all be public or all private.
H. UNIX—Options to be used in mounting the VOB. The following options are valid: ro, rw, soft, hard, intr, nointr, noac, noauto, nodev, nodnlc, nosuid, suid, retrans, timeo, acdirmin, acdirmax, acregmin, acregmax, actimeo. See the appropriate operating system reference page (for example, mount(1M)) for the meanings of these options. If the mount options list contains white space, enclose it in quotes. By default, a VOB is mounted in nointr mode. This means that operations on MVFS files (for example, open(2)) cannot be interrupted by typing the INTR character (typically, CTRL+C). To enable keyboard interrupts of such operations, use the intr mount option. Windows—Specifies mount options to be invoked when the VOB is activated through this VOB tag. See mount for details. (You must be a member of the ClearCase group to use this option.)
I. ClearCase on UNIX: Marking a VOB for export. A VOB to be used by some view for NFS access must be marked for export. Each export VOB is assigned an export ID, which ensures that NFS-exported view/VOB combinations have stable NFS file handles across server reboots or shutdown and restart of ClearCase. If the VOB is registered in multiple regions, the export marking must appear on all of that VOB's tags in all the regions in which it is registered. To mark a VOB for export, use the –ncaexported option. To mark an existing VOB for export, use mktag –replace –ncaexported.
The VOB export ID is stored in the mount options field in the VOB tag registry. If you use the –ncaexported option and specify additional mount options in the mktag or mkvob command, the mount options field includes an appropriate export ID mount option.
For information about exporting VOBs, see the export_mvfs reference page.
Note: Marking a VOB for export is not required for NFS export to work, but it is required if you want to avoid stale file handle messages after a server restart.
J. To use the -nremote_admin option, you must be logged on the the VOB server host as a privileged user.
K. ClearCase dynamic views: Public and private VOBs. Some VOBs are to be shared, and others are to be used primarily by their creators. Accordingly, there are two kinds of VOB tags: public and private.
UNIX: Public VOB tags
A public VOB tag specifies a location at which any dynamic-view user can mount the VOB. Furthermore, after a public VOB is mounted on a host, any user on that host can access it (subject to the standard access permissions).
Typically, all public VOBs are mounted at startup time with the command cleartool mount –all. (To create a public VOB that is not mounted automatically, specify –options noauto in the mkvob command.)
When creating a public VOB tag with mkvob or mktag, you must supply the network's VOB tag password; if you do not use the –password option, you are prompted to provide one.
You need not create a public VOB's mount-over directory; the cleartool mount command creates it, if necessary.
UNIX: Private VOB tags
A private VOB tag specifies a mount point at which only the VOB's owner (usually, its creator) can mount the VOB using cleartool. For example:
cleartool mount /vobs/myPrivateVob
root can use the cleartool mount vob-tag command to bypass the “owner only” mount restriction. The command cleartool mount –all does not mount private VOBs. After a private VOB is mounted, any user can access it (subject to the standard access permissions). You must explicitly create the mount-over directory for a private VOB; the cleartool mount command does not create it automatically.
Windows: Public VOB tags
A public VOB can be activated with the following command: cmd-context mount –all
Usually, the system administrator automates this command for users in either of two ways:
1. By adding it to the startup script for ClearCase users.
2. By supplying it in a batch file for use in each user's Startup folder.
This technique is particularly useful because, in its role as a network provider, the MVFS deactivates all VOBs and views on the local host at user logon time. That is, each time a user logs on, the dynamic-views drive (by default, drive M) is empty until VOBs and views are reactivated.
For information on persistent VOB mounting, see the mount reference page. When creating a public VOB tag with mkvob or mktag, you must supply the network's VOB tag password; if you do not use the –password option, you are prompted to type one. For information on how to create or change the VOB registry password, see rgy_passwd.
Windows: Private VOB tags
Any user can mount any VOB, public or private. The private designation means only that a VOB must be mounted separately, by name.
UNIX and Windows: Private-to-public VOB conversion
To convert a private VOB to a public VOB, use a command like this:
cmd-context mktag -vob -tag \vob3-replace -public \\saturn\users\vbstore\private3.vbs
This replaces the VOB's private VOB tag with a public one. mktag prompts you to enter the VOB tag password. ClearCase and Clearcase LT snapshot views: Accessing public and private VOBs. For an explanation of public and private VOBs, see ClearCase dynamic views: Activating the VOB. ClearCase: Snapshot views make no distinction between public and private VOBs: you can access private VOBs from a snapshot view regardless of who owns them. ClearCase LT: All VOBs are private and can be accessed from any view.
ClearCase: Location of the VOB database directory.
The VOB database directory must be located on the VOB server host or on a
supported network attached storage device that has been configured for VOB
storage. For a discussion of network attached storage devices, see the IBM
Rational ClearCase Administrator's Guide. To create a VOB that resides on a
supported network attached storage (NAS) device, you must specify the option
set, –host –hpath –gpath .
M. If you specify –auto, a server storage location for the VOB is selected as follows:
Server storage locations that have no global path (mkstgloc –ngpath) and that reside on remote hosts are disqualified. Server storage locations on heterogeneous hosts are disqualified. Local server storage locations are preferred over remote ones. Globally accessible server storage locations (mkstgloc –gpath) are preferred over those that are not (mkstgloc –ngpath). The server storage location with the most free space is selected.
N. Specifies a server storage location in which the VOB storage directory is to be created. The server storage location must have been created previously with mkstgloc. You can specify the name of the VOB server storage location explicitly as vob-stgloc-name, or specify –auto to direct mkvob to select one.
O. The location at which a new VOB storage directory is to be created. (An error occurs if something already exists at this path name.) You can create a VOB at any location where the operating system allows you to create a subdirectory, with these restrictions:
1. You cannot create a VOB under an existing VOB tag (VOB mount point).
2. You cannot create a VOB within the view root directory.
3. vob-storage-pname must not be a subdirectory of an existing VOB storage directory.
4. vob-storage-pname must specify a location on a host where ClearCase has been installed or a location on a supported NAS device. The VOB database (located in subdirectory db of the VOB storage directory) must be located on the VOB server host or on a supported NAS device that has been configured for VOB storage.
5. UNIX—vob-storage-pname may be a full path name, relative path name, or simple subdirectory name. For related information, see the description of CCASE_GPATH_HINTS in the env_ccase reference page.
6. Windows—vob-storage-pname must be a UNC name.
Note: All the command below rely on there being a ccvovbstore directory, in the root directory at UNIX or as a Shared drive in Windows. The /net/samecs mount assumes a hostname of samecs, which has been either hard mounted or auto-mounted on /net in UNIX.
cleartool mkvob –tag /vobs/samecs_pvob –ucm –c “SAMECS UCM Project VOB” –public –password 1qaz2wsx –host vobserver.samecs.com –hpath /net/samecs/ccvobstore/samecs_pvob.vbs –gpath /net/samecs/ccvobstore/samecs_pvob.vbs hpath /net/samecs/ccvobstore/samecs_pvob.vbs
cleartool mkvob –tag \samecs_pvob –ucmproject –c “SAMECS UCM Project VOB” –public –password 1qaz2wsx –stgloc samecs_vob_storage
cleartool mkvob –tag /vobs/samecs_admin –c “SAMECS Admin VOB” –public –password 1qaz2wsx –stgloc samecs_vob_storage
A combination of an export VOB and Views allows you, via NFS, to dynamically access a VOB on an architecture that does not support, or on a server where you do not want to install ClearCase. See using export VOBs and Views.
cleartool mkvob –tag /vobs/samecs_pvob –c “SAMECS export VOB” –public –password 1qaz2wsx –nca –host vobserver.samecs.com –hpath /net/samecs/ccvobstore/samecs_export_vob.vbs –gpath /net/samecs/ccvobstore/samecs_export.vbs hpath /net/samecs/ccvobstore/samecs_export.vbs