Rational® ClearCase® and ClearCase MultiSite®

ClearCase and MultiSite Version 2002.05.00 run on the platforms listed in Table 1.1..

For more information about differences in features and functionality by platform, see the ClearCase Platform-Specific Guide in online help. To access the platform guide, go to ClearCase help and click Help Topics.

The following platforms support a ClearCase Web server:

All supported ClearCase platforms support the ClearCase Web interface. For details about the Web servers and Web browsers supported on different platforms, see the section called “Basic Software Requirements ”.

Table 1.2. lists the file systems that ClearCase supports. If a file system does not appear on the list, it is not supported. Inform Rational Technical Support or your sales representative of any concerns you have about this list.

This section describes hardware requirements for installing and running ClearCase and MultiSite.

This section describes software requirements for running ClearCase and MultiSite.

You can find up-to-date information on Microsoft Windows operating system issues at the Microsoft Web site, www.microsoft.com.

The Installation Guide for the ClearCase Product Family provides information necessary to install the ClearCase family of products. Here is some general information to keep in mind about upgrading:

See also the section called “Known Issues Related to Installation”.

This version of ClearCase introduces a new feature level, FL3, to support some of its new functionality. To upgrade to the new feature level, you must upgrade systems to the new feature level in the correct order after installing Version 2002.05.00 on all the view and VOB server systems. If you are using UCM, this order is different from the order required at previous releases of ClearCase and MultiSite. The order is:

Note that in a UCM environment, if you do not perform Step 5, client systems that have not been upgraded to the new release will not operate.

If servers are upgraded to the Version 2002.05.00 before all client systems have beem upgraded, new VOBs must be created on servers that run ClearCase Release 4.x, because Release 4.x clients cannot communicate with VOBs created on systems that run the new release.

Once you upgrade the feature level on your PVOBs, you must also set the recommended baselines on integration streams that are in use. If you do not, existing development stream configurations may be unexpectedly changed when you perform a rebase -recommend command.

For more information, see the ClearCase white paper on migrating to Version 2002.05.00 on the Rational Web site, www.rational.com/support/products/clearcase.jsp.

The way in which you evaluate Version 2002.05.00 depends on which release of ClearCase you are currently running.

If you are running a 4.x release and you want to evaluate Version 2002.05.00, you can install this version on one or more test systems in your existing environment of servers, clients, views, and VOBs, and configure the test systems to use your 4.x license server.

Alternatively, you can install Version 2002.05.00 in evaluation mode on a test system. For more information on evaluation mode, see the Installation Guide for the ClearCase Product Family.

Even the simplest ClearCase operation invokes a communications chain that can involve several components. For example, the act of checking out a file element involves a client program (running on the developer's workstation), which acts through a particular view (located on that workstation or elsewhere) and uses a particular VOB (typically located on a dedicated VOB server host). If all the components in this operation are running the same ClearCase release, compatibility is guaranteed.

Table 1.7., Table 1.8., and Table 1.9. show the compatibility paths if all hosts are not running the same ClearCase release. In these tables, client means ClearCase client software. In each table, a component in a row can use a component in a column if there is a yes at the intersection of the row and column. For example, Table 1.7. shows that a 4.x view can use a 2002.05.00 VOB or a 4.x VOB, but a 2002.05.00 view cannot use a 4.x VOB.

Specifically, these tables make two points:

In general, 4.x clients can access 4.x and 2002.05.00 servers, while 2002.05.00 clients can access 2002.05.00 servers only. A notable exception is that 2002.05.00 clients and servers will talk to 4.x albd_servers to support access to registry, license and other administrative functions.

A Version 2002.05.00 client on UNIX can access a VOB on Windows NT using a snapshot view. However, the snapshot view storage directory and the VOB storage directory must be on servers running Version 2002.05.00 or later.

Prior to Release 4.1, view and VOB storage locations were supported only on Windows servers. Release 4.1 added enhanced support for creating and managing storage locations. To enable Version 2002.05.00 clients to use storage locations set up in a release prior to 4.1, you must upgrade those storage locations.

Rational recommends that you reformat your VOBs to use schema version 54 as soon as possible. If you are considering conversion or migration to Microsoft Active Directory, schema 54 is required. Schema version 54 provides improved support for multiple domains, domain migration, as well as supporting ClearCase use with an Active Directory.

ClearCase MultiSite Version 2002.05.00 is fully compatible with ClearCase Version 2002.05.00 client and server hosts:

The following sections describe compatibility restrictions and issues when different sites are running different MultiSite releases.

See the Installation Guide for the ClearCase Product Family for detailed information about installing and licensing ClearCase and MultiSite software.

This section discusses restrictions or defects that involve the installation of the ClearCase product. Take into account the information in this section before or during installation to be sure that ClearCase software or particular features are installed properly.

Assertion failed!
Program: path-name
File: file-name
Line: line-number
Expression: "Function not implemented: " ...
For information on how your program can cause an assertion failure, 
    see the Visual C++ documentation on asserts.
(Press Retry to debug the application - JIT must be enabled.)

Error 1069: ClearCase ALBD could not log in due to wrong password

In the basic UCM process, the integration stream is the project's only shared work area. You may want to create additional shared work areas for developers who work together on specific parts of the project. Now you can accomplish this by creating a hierarchy of development streams. For example, you can create a development stream and designate it as the shared work area for the developers working on a particular feature. Developers then create their own development streams and views under the feature-specific development stream. In other words, the developers join the project at the feature-specific development stream level rather than at the integration stream level. The developers deliver work to the feature-specific development stream and rebase their streams to recommended baselines in the that development stream.

You can now deliver work from an integration stream or a development stream in one project to an integration stream or development stream in another project. In addition, you can deliver work from one development stream to another within a project. These features make it easier to manage related areas of development within a project, and parallel releases of multiple projects.

The default target for a deliver operation is the source stream's parent stream. You can also deliver work to nondefault target streams. Because any stream can now be the target of a deliver operation, this release adds several policies that you can set on streams to control what kind of deliver operations the target stream will accept. For example, you can set a policy to reject deliver operations that contain changes to components that are not in the target stream's configuration. You can set these policies at the project level so that the policy settings apply to all streams within the project, or you can set the policies on a per-stream basis.

A baseline selects one version of every element visible in a component. This release lets you create composite baselines. A composite baseline is a baseline that selects baselines from other components. By creating a composite baseline that selects baselines from every component in your project, you can use one baseline to represent the entire project.

After you create a composite baseline to represent the project, the next time you invoke the make baseline operation on the composite baseline, UCM performs the operation recursively. If a component that contributes to the composite baseline has changed since its latest baseline, UCM creates a new baseline in that component.

A composite baseline can select other composite baselines. This feature allows you to use a composite baseline to represent a system that consists of multiple projects. The system-level composite baseline can select project-level composite baselines.

You now have greater flexibility in storing components in VOBs. For example, you can now store multiple components in a VOB. Within a VOB you can make an existing directory tree into a component. The component's root directory must be the VOB's root directory or one level beneath it. To store multiple components within a VOB, each component's root directory must be one level beneath the VOB's root directory.

This release adds support for triggers to the following UCM operations

Other new features in this product release include:

This version of the ClearCase Web interface supports the UCM developer role. A developer can use the Web interface to join a project, create new activities, perform work in those activities, deliver work to an integration stream, and rebase a development stream to recommended baselines.

Performing the UCM rebase or deliver operation requires the ability to merge changes in files. The ClearCase DiffMerge tool has been implemented for this purpose within the Web interface context. The DiffMerge tool is called automatically when you do a rebase or deliver operation from within the Web interface; you canalso run the Merge Manager directly from the Web interface toolbar.

ClearCase now provides workspace management capabilities for Web views which are similar to those for standard ClearCase snapshot view functionality on a local copy of element versions.

A new configuration variable has been added to the ccweb.conf file to control the length of time that elapses before an unattended ClearCase Web session times out. The new variable is ‘-session_timeout age_in_seconds' where the minimum value for age_in_seconds is 600 (10 minutes) and the default value is 14400 (4 hours).

It is now possible to specify "interop text mode" as a characteristic of a ClearCase Web view during the view creation process.

Installing the ClearCase Web server components is now optional; previously these components had been installed on all systems.

If you are installing a ClearCase server, the ClearCase Server Options window now includes a check box for installing Web Server Interface Components; the default is to install the option If you are installing a ClearCase client, you must select a Custom installation to install the Web interface components. First select Custom on the Select Configuration dialog, then select the component as desired on the subsequent Choose Features dialog. a new option has been added to the installation.

The online help for the ClearCase Web interface has been updated to reflect the enhanced functionality of this feature. In addition, the chapter Configuring a Web Server for the ClearCase Interface in the Administrator's Guide for Rational ClearCase contains updated information on configuring the ClearCase Web server.

The ClearCase PowerBuilder integration has been enhanced to fully automate the deliver and rebase operations. Users can now perform deliver and rebase operations on PowerBuilder Library (PBL) objects. They can also recreate PBLs from versioned objects.

Forte Developer V6.0 now supports a ClearCase integration. This integration provides a set of commands and tools that allow a software development team to share, control and track files created with Forte Developer.

Using this integration, you can check out, modify, and check in your files without leaving the Forte Developer IDE or starting another application. You can also use this integration to access files under version control.

You can access commands and tools supported by the integration from the Forte Developer's Tools menu.

The following ClearCase commands and tools are available:

The above commands and tools give you all the capabilities you generally need.

This version of ClearCase provides an SCC-level integration of ClearCase functionality with Microsoft's Visual Studio version 7 (Visual Studio.NET). Support for the ClearCase toolbar add-in will be available through a ClearCase patch.

ClearCase Version 2002.05.00 includes an updated integration with Microsoft Word that uses a COM add-in. Because the COM technology is incompatible with Word 97, this new integration only works with Word 2000 or Word XP.

However, the old integration is not removed if Word 97 is still installed. If both Word 97 and Word 2000/Word XP are installed, the old integration continues to work with Word 97, while the new integration is installed for use with Word 2000/Word XP.

Silent install is a method of installing Rational ClearCase on client systems, without intervention from users. The silent install greatly reduces the work of an administrator during a rollout of ClearCase. It also ensures that the correct software configuration is installed on each target system. The procedures and guidelines for implementing the silent install are available in the Installation Guide for the ClearCase Product Family.

When upgrading from ClearCase LT to full-featured ClearCase, the installation process now runs the ClearCase LT upgrade tool in the background instead of having the user invoke it from the command line. More information on the ClearCase LT upgrade tool is available in the Installation Guide for the ClearCase Product Family.

Previous versions of ClearCase did not upgrade the VOB database format to schema 54 when specified in the Site Preparation Wizard. In this version, ClearCase does perform the upgrade to schema 54. It also displays a message reminding users to reformat the VOBs stored on the local machine, as a result of the upgrade.

During ClearCase site preparation, when setting site-specific defaults, you can define the tool shortcuts definition file for ClearCase Explorer (see the section called “Enhancements to ClearCase Explorer”). This file allows you to remove shortcuts that Rational defines and substitute your own for a site and add shortcuts to locally used tools and URLs.

The installation program has been enhanced to produce a log file that documents the installation process. This file includes information about the version of the installation program used, the ClearCase LT configuration installed, the files and patches installed, and the completion status.

The installation log is created by setting the /log option when invoking the setup command. The log file is written to the location ccase-home-dir\install\ccsetup.log.

More information on generating and viewing ccsetup.log is described in the Installation Guide.

The MVFS Settings dialog box in the ClearCase Site Preparation Wizard and the ClearCase Installation wizards now allow you to specify two additional settings:

For considerations in selecting the values of these settings, see the online help. You can also modify these settings from the ClearCase Control Panel.

In this version of ClearCase, the installation process will carry forward custom type managers that had been installed under previous versions. Note that a copy of the ccase-home-dir\lib\mgrs\map file is saved under the name map.save, and information about the action taken is written to the ccsetup.log file, when it is generated

In earlier versions of ClearCase, a ClearCase_ALBD account name inadvertently entered with a blank space at the beginning or end was treated as a unique account name separate from the same name entered without the space. Now spaces at the beginning or end of the ClearCase_ALBD account name will be ignored.

This release supports ClearCase execution of parallel builds on Windows NT platforms when using clearmake. ClearCase can perform builds in which multiple processes execute in parallel the build scripts associated with makefile targets. The processes that execute the build scripts must all run on a single machine. By using more concurrent processes, parallel builds can reduce the overall build time significantly. Instead of one process running one script at a time, you can have multiple processors working in parallel. Within large software systems, this feature can substantially improve system performance. fFor more information, see the Building Software manual (Windows Edition).

clearmake now offers support to record the versions of makefiles, and optionally to have changes to them affect reuse of derived objects. Two new makefile special targets have been added: .MAKEFILES_IN_CONFIG_REC and .MAKEFILES_AFFECT_REUSE. The .MAKEFILES_IN_CONFIG_REC special target causes makefiles read by a build session to be recorded in the configuration record of all derived objects built during that build session. You can use the .MAKEFILES_AFFECT_REUSE special target to specify changes to makefiles as criteria affecting the reuse of derived objects during builds. For more information, see the Building Software for Rational ClearCase.

When clearmake rebuilds a target because a "build script mismatch" is detected, you can now use the -d and -v options to generate a print of the actual script differences to standard output.

Clearmake -C gnu now allows special characters such as ";" to be used in macro names.

Clearmake now supports the use of special characters such as "$$" (as an equivalent to a literal "$") or "\%" (as the string literal "%") in target names. This has been implemented by default for -C gnu, and through the .JAVA_TGTS special target for all other compatibility modes.

This release has enhanced support for sharing of dynamic views and VOBs across complex Active Directory configurations.

This support makes it easier for a community of ClearCase users to share dynamic views and VOBs across multiple Active Directory domains in a single forest. Earlier ClearCase releases supported this capability, but may have required workarounds to make dynamic views operate in multiple Active Directory domains in a single forest. This release no longer requires workarounds such as creating direct trust relationships or ensuring dynamic views have more liberal read/write access when created.

chevent type triggers now fire correctly when a trigger is set on MODIFY_TYPE. The chevent operation for element triggers is now a sub-operation of the MODIFY_ELEM operation rather than the MODIFY_MD and MODIFY_DATA operations that it fell under previously.

Operations which enumerate the contents of VOB or view-private directories (such as /bin/ls on UNIX, dir on Windows in a command shell,; or Explorer windows on Windows) can be accelerated by MVFS caching of the directory contents. Directory contents at the MVFS level are handled in blocks of entries. This value determines the upper limit of how many blocks can be cached per directory. The default setting of 4 blocks is enough space for approximately 600 directory entries.

For more information, see the Administrator's Guide.

The clearimport command now checks for VOB locks before processing an element or version. If it detects a VOB lock, it shows a message indicating that the VOB is locked and that it will wait 60 seconds to retry. It remains in this state until either the VOB is unlocked or the user interrupts the import.

Beginning with thise version of ClearCase, use of rmelem is restricted to the VOB owner or privileged user unless no versions have metadata (labels, attributes, or hyperlinks) and all branches were created by the user.

Removing a VOB symbolic link with the rmelem command now causes all-element rmelem triggers to fire. This works only for all-element trigger types and does not work with per-instance triggers.

The view_server now dumps and/or loads very large views. Previously it would fail to dump or load a view if the dump file exceeded 2 GB in size. The view_server now creates multiple dump files for very large views, each of which is limited to about 1 GB in size.

Previously, when diffbl failed comparing imported baselines, initial baselines, or baselines/streams based off imported or initial baselines, against other similar baselines or streams, it displayed confusing error messages. These messages described the failure as resulting from the fact that the baselines or streams involved did "not share a common ancestor (initial or imported) baseline".

Now the error message describes the cause of the failure more accurately as resulting from the fact that the baselines/streams "are derived from different import baselines or the initial baseline".

Table 2.1. lists new commands in this version of ClearCase. In addition, the clearprompt command is now available as part of the minimal developer installation.

Table 2.2. lists new options and arguments to commands in this version of Rational ClearCase.

The -title title option/argument pair, previously used by the ClearCase commands chfolder, chproject, chstream, mkfolder, mkproject, and mkstream, is obsolete at this release of the product.

In addition, the -generate old-object-selector option to the rename command is also obsolete.

The clearexport_ffile command is obsolete; use clearfsimport instead.

Redefinition of element types (mkeltype -replace) is no longer allowed in replicated VOBs.

The ClearCase Command Reference is now published in a single edition for both UNIX and Windows. At the beginning of each reference page are tables that show the platforms and ClearCase Product Family products to which the interface described applies.

The first chapter of the Release Notes for Rational ClearCase and ClearCase MultiSite (this document) has been reorganized. All the material related to basic hardware and software requirements for installing and running the products has been moved to a single section titled Hardware and Software Requirements in the READ_ME_FIRST chapter, to make it easier for customers to prepare for installation of new versions of the products.

Large sections of material in the Command Reference have been moved to other manuals, and some material from Building Software has been moved to the Command Reference.

In previous releases, restrictions for commands were in a section called PERMISSIONS AND LOCKS. In this release, the section is named RESTRICTIONS. The section that was previously named Permissions Checking is now called Identities. There is a new section named Mastership, which describes any restrictions applied when the command is run in a replicated VOB.

The msdostext_mode reference page now describes the options -r and -f. The -r option resets the line counters for elements of type text_file that have been changed to a binary type, and the -f option forces a recalculation of the line count of all VOB objects of type text_file.

The following sections describe the changes to command output in this release.

2002.05.00

This version of ClearCase introduces a new feature level, Feature Level 3 (FL3). To support all of the new UCM functionality provided with the new release, a PVOB must be upgraded to the new feature level. Until a 2002.05.00 PVOB has been upgraded to FL3, it will support ClearCase Release 4.x clients as well as Version 2002.05.00 clients, but without providing support for all the new UCM functionality delivered with the new release.

Specifically, the following new features are not supported, even on 2002.05.00 clients accessing 2002.05.00 servers, until the feature level of the associated PVOB has been raised to FL3:

Installing this software on a PVOB server that is running a previous release of ClearCase does not automatically change the PVOB's feature level; you must raise the feature level manually. Before raising the feature level, all ClearCase clients accessing that PVOB must be upgraded to Version 2002.05.00. ClearCase UCM operations will fail on clients that run previous versions of ClearCase if they try to access a PVOB whose feature level has been upgraded to FL3.

This release of ClearCase supports the ability to change a stream's configuration from one using a modifiable component to one using a nonmodifiable one. However, we generally recommend that components initially be specified to be nonmodifiable when creating a new project. After verifying that the project builds and tests correctly, update the project policies to allow modifications to any or all components.

If, in a UCM view, you check out or check in an element from a VOB that is not a UCM component, you should not have to select an activity, because that operation is not captured in a change set.

However, if you are in a view that is in a ClearQuest-enabled project, both the Check Out dialog box and the Check In dialog box force you to select an activity even though one is not really required.

Workaround: Select the activity; it will be ignored.

When you join a project in which the integration stream is not mastered by your current replica, you can create a development stream and view, but not an integration view. The Join Project Wizard displays a message that you will not be able to create an integration view; but when you click Finish, the wizard attempts to create the integration view and fails. If creation of the development view and stream succeeded, you can ignore the error.

The UCM process in ClearCase is enhanced for sites that have installed Rational ClearQuest by a very tight integration between the activity management provided by UCM and the change request management provided by ClearQuest. Use the following guidelines with the UCM-ClearQuest integration.

An error occurred during the deliver.
Unexpected error in deliver.

A stream can be rebased to a baseline that meets the following criteria:.

Additional rules apply to integration streams and development streams in selecting a baseline

Rebase is typically used to advance a stream's configuration; that is, to replace its current foundation baselines with more recent ones. However, under certain conditions, rebase can be used to revert a baseline, and to add or drop a component in a stream's configuration. It can also switch to a baseline that is neither an ancestor nor a descendant of the current foundation. The rules explained above are general rules for all rebase operations. You need to satisfy only the general rules when adding a component to a stream. When you advance, revert, drop or switch a baseline, you need to satisfy the general rules and some additional ones.

To advance a stream's configuration, the new baseline must contain the current foundation baseline.

To revert or drop a baseline for a component in a stream, one of the following conditions must be met:

To switch to a baseline that is neither an ancestor nor a descendant of the current foundation, one of the following conditions must be met:

These rules ensure that any changes made in a stream are not lost when the configuration changes.

If a baseline is recommended for a stream, and then that baseline is removed, clear the recommended baseline setting in the stream by typing the command chstream -nrecommended. Then you can set new recommended baselines by using the command chstream -recommended.

Attache users cannot use ClearCase UCM commands.

Deliver cannot allow changes to a read-only component. This situation can result from someone changing the component modifiability in your project. What actions you take depend on whether you are doing an intraproject or an interproject deliver.

You can recommend a baseline for a stream if the baseline is from the stream or the stream's foundation.

For a baseline not from the stream or the stream's foundation, the following rules apply:

You are not required to recommend a baseline for every component in the stream's configuration.

You can clear the list of recommended baselines. Note that doing this step alone will cause problems when existing development streams rebase to the recommended baselines. The rebase operation will attempt to drop all baselines in the development streams' configuration. This operation will probably fail or produce errors and therefore not desirable.

You can choose to reset the recommended baselines to baselines from the stream or the stream's foundation with or without clearing the recommended list. This allows the stream to return to a known correct state after being changed inadvertently to a bad list.

Delivering selected activities to a non-default target is subject to the following restrictions:

It is possible for a remote deliver to include changes to a component when the component is non-modifiable in the project. This only happens when the remote site has not synchronized with the local site, and does not know that the component has been made non-modifiable. When the integrator attempts to resume the remote deliver, a check is made to ensure that no versions in non-modifiable components will be changed. If there are such versions in the deliver, the operation fails and the user has to cancel the deliver.

In this release, the integration includes a new trigger, which runs on Windows and UNIX platforms. The release includes the source code, in the form of Perl scripts, that the trigger uses. The Perl scripts include extensive comments that describe the purpose of their classes. For additional source code documentation, including an architectural overview and formatted class documentation, contact Rational Customer Support. However, Rational Customer Support cannot and will not support changes that you make to this source code.

The base ClearCase-ClearQuest integration creates a ClearCase tab on your ClearQuest screen. On this tab, if you right-click CC Change Set Objects and then select View Details, the program displays data about a VOB element. If the version-extended pathname is too long to fit in the dialog box, it cannot be viewed in its entirety, because the form does not support horizontal scrolling by default. You may want to modify the form using the following procedure:

If you wanted only the horizontal scrollbase on the name, do the following instead:

If you are using the Web interface in a UCM environment, you cannot use the Web interface to work effectively in projects enabled for ClearQuest. You can view such projects, but you cannot perform any integration operations through the Web interface; also, you cannot use the interface as a suitable client in a UCM project enabled for ClearQuest.

The ClearCase Web interface supports noninteractive triggers. Interactive triggers, such as those that attempt to read input or create a window, fail.

If a trigger attempts to read input using clearprompt, the ClearCase Web interface prints this error:

clearprompt is not supported in the Web interface

If a trigger attempts to read directly from standard input, it receives an error, because standard input does not specify a valid file descriptor.

In addition, any trigger failure in the Web interface context displays this error message:

Interactive triggers are not supported in the Web interface. If the trigger was interactive, it may have failed for that reason.

Trigger script writers can detect whether a trigger is running in the Web interface context by checking for the environment variable ATRIA_WEB_GUI. It is set to 1 if you are running in the Web interface context.

Note that the base ClearCase-ClearQuest integration is dependent on the operation of interactive triggers; for this reason, the ClearCase Web interface is not a viable interface for using that integration.

The Web interface does not support graphical (tree view) comparison of XML file elements; the Web Compare tool displays a text-based comparison for elements of type xml. When comparing HTML files, the program displays the differences in the Compare screen as text, but includes hyperlinks to display the individual files appropriately formatted using your default browser.

In addition, because the Compare tool in the Web interface handles only text files, it does not support comparison of Rational Rose or Microsoft Word files.

Windows NT 4.0 sends very large amounts of information to a Web server. This behavior causes the ClearCase Web interface to fail when attempting to check in very large files (on the order of several megabytes). This problem appears to be fixed in Windows 2000.

The Java program used in the Web interface attempts to connect to the Web server to transfer files. Web browsers only allow Java programs to open connections to the server from which the programs were downloaded.

To enforce this rule, the Web browser on the Web interface client must be able to resolve the Web server's host name to an IP address. If you use a host name in a URL that cannot be resolved by the client host, the Java program cannot connect to the server. In this case, Web-interface file-transfer operations such as checkout, checkin, and download fail.

If the Web server is being accessed through a firewall by means of a proxy server, the proxy server being used must support DNS lookup outside the firewall.

When the ClearCase Web server on Windows logs on to a client, it sets the primary group to the designated primary group in the client user's domain account. In Release 4.0, you could not override this group setting. As a result, sites that use domain mapping to allow user accounts in multiple domains to share VOBs could not access those VOBs through the ClearCase Web interface.

Workaround: Specify a configuration variable in the ccweb.conf file, and add a value to the registry that enables domain mapping.

Toolbar popup menus don't close properly when running the Web interface using Netscape Navigator. Rather than closing automatically when the mouse pointer is moved out of the menu location, they close only when you must reselect the menu button.

If you access the ClearCase Web interface using a Netscape browser on a Windows system and also use a version of the Exceed X Windows Server earlier than 6.0, do not let the Netscape window lose its focus to an Exceed window. Doing so causes the Netscape window to restart any Java applets it is currently running, which interferes with file transfer operations, for example, download, checkout, or checkin.

Neither Internet Explorer nor Version 6.0 of the Exceed X Server has this problem.

In order to run the Web interface successfully, the Internet Explorer setting 'Check for newer versions of stored page' should be set to the value "Automatically." To access this setting, click on Internet Explorer ->Tools->Internet Options->Temporary Internet Files->Settings->Check for newer versions of stored page.

The Windows version of the iPlanet Web server does not allow a pathname for an "Additional Document Directory" to contain spaces. Since the ClearCase Web interface requires configuration as an "Additional Document Directory" mapping to the "web" directory under the ClearCase installation directory, ClearCase cannot be installed in a location which contains spaces (for example the 'Program Files' directory) if the iPlanet web server is expected to provide the ClearCase Web interface.

Web views can only be accessed via the Web interface; they cannot be used with native ClearCase interfaces (for example ClearCase Explorer or cleartool). Various native GUIs may allow selection of a Web view (for example as a deliver target), but any attempt to access a Web view using a native ClearCase interfaces will result in a warning or error message.

Rational ClearCase 2002.05.00 introduces a new ClearCase Web interface. This interface is not compatible with Web views created by previous ClearCase Web interface clients. If you want to re-use existing Web views, we recommend that you clean them up before you upgrade the ClearCase Web server host to ClearCase 5.0.

Use the following procedure:

ClearCase is integrated to work with FrontPage 98, FrontPage 2000, Visual InterDev, Microsoft's Save to Web Office 2000 functionality (Word, Excel, PowerPoint), and Microsoft Internet Explorer 5 (IE5) Web Folders.

When using ClearCase with these programs and tools, follow the guidelines below:

The integration of ClearCase Version 2002.05.00 and Visual InterDev may cause corruption and data loss. The problem occurs when user A checks out a file and then user B checks out the same file; user A is permitted to check in before user B. When attempting to check in the file, user A receives an error message and the file becomes corrupt.

There are three ways to deal with multiple-checkout problems in Visual InterDev:

To use the ClearCase integration with Visual Studio, users must do one of the following:

ClearCase uses the Microsoft Common Source Code Control (SCC) interface to integrate with the Microsoft Visual C++ available through Microsoft Visual Studio. ClearCase has support for Visual C++ versions 5.0 and 6.0. You can switch between SCC-support versions 5.0 and 6.0, but only one version can be enabled at a time.

The ClearCase SCC interface for Visual C++ 6.0 also supports Visual Basic 6.0, Visual J++ 1.1, and Visual InterDev 6.0.

Using ClearCase with Visual Studio components requires no special configuration on the part of the user. For more information, see the information on Developing Software in online help.

cleartool checkout .
cleartool mv foobar FooBar
cleartool mv ...
...
cleartool checkin . 

Use the following guidelines when using the ClearCase integration with Microsoft Visual Basic.

Follow the guidelines below when using the Version 2002.05.00 integration with Microsoft Word.

Using the ClearCase integration with PowerBuilder requires some configuration steps. In addition, there are some differences between the integration with PowerBuilder 6.x and PowerBuilder 7.x.

The following commands require NFS or SMB access to the VOB storage directory when it resides on a UNIX host:

In NFS products with UNC support, do not enable automatic mounting of NFS-storage directories. If you enable automatic mounting, you may experience problems starting views and VOBs located on UNIX hosts.

The following problem relevant to ClearCase exists in the Command Reference.

The Developing Software manual for ClearCase is missing information relating to the following topics.

The deliver operation is unable to access the root of the 
'%s' snapshot view. 
(Before trying again, make sure that you can access 
ClearCase properties by right-clicking on the view's root 
directory in the Windows explorer.) 

Because of a change in the scaling algorithm, Table 13 on page 507 of the Administrator's Guide for Rational ClearCase shows incorrect values for the effect of memory size on the MVFS Scaling Factor for memory sizes greater than 256 MB. The corrected values are:

The largest value that the Scaling Factor is automatically set to is 24.

The following issues exist with online help.

This section describes problems with running tutorials.