Configuring non-ClearCase access on Linux or the UNIX system

A host running Linux or the UNIX system on which DevOps Code ClearCase has not been installed can read VOB data from a VOB server running Linux or the UNIX system. Typically, the technique is as follows:

• A host running Linux or the UNIX system and DevOps Code ClearCase must export a view-extended pathname to the VOB mount point (for example, /view/exportvu/vobs/vegaproj). Edit the file /etc/exports.mvfs to specify this pathname.
• One or more non-ClearCase hosts access the VOB through a view-extended pathname. For example, a host may have an entry in its file-system table that begins

  mars:/view/exportvu/vobs/vegaproj /usr/vega nfs ...

Non-ClearCase access carries several restrictions:

• VOB access. Users on the non-ClearCase host can read, but cannot modify, data from VOBs on VOB server hosts running Linux or the UNIX system that have been configured for non-ClearCase access. They are also restricted to using the element versions selected by the specified view; they cannot use version-extended or view-extended pathnames to access other versions of the VOB's elements.
• Building. Although users cannot modify VOBs that are accessed through an export view, they can write to view-private storage. Users can modify these view-private files with an editor and build them, though not with clearmake. Files created by such builds do not become derived objects; they are view-private files, unless developers take steps to convert them. (For more information, see DevOps Code ClearCase Guide to Building Software.)
• Because clearmake and other build-management tools do not run on the non-ClearCase host, configuration lookup and DO sharing are not available.