The ClearCase Type Explorer and Properties Browser always display information about local copies of global types, instead of displaying information about the global type.

If the client VOB you are browsing does not contain a local copy of a global type, the ClearCase Type Explorer does not display the global type.

The cleartool diffbl command, which compares two baselines and shows the differences between them, does not work correctly when one or both of the baselines are imported baselines.

VOB symbolic links are limited to one level of indirection in snapshot views. That is, the result of cleartool ln –s is loaded as a native file-system symbolic link only if the target of the symbolic lin is not another VOB symbolic link.

In the Project Explorer, the Activities tab of the baseline and integration stream property sheets does not list the activities that have been delivered to the integration stream and incorporated into the baseline. The Activities tab displays only activities that were created in the integration stream, including integration activities, which ClearCase generates during deliver operations.

In a UNIX snapshot view, your config spec may not be correctly synchronized before all update previews. However, synchronization is always correct for full updates.

If you create a new element in one activity (for example, A) while the directory containing the element is checked out to a different activity (for example, B), you have created an implicit dependency of A on B. When selectively delivering activity A, you must also include activity B. Otherwise deliver reports the error: DBID not found.

The Transcript window may open when exception conditions have occurred during an operation. When the Transcript window and another modal dialog box are open, such as a properties dialog in which operations can be initiated, the Transcript window does not respond to user actions. You must close the dialog box before you can adjust the scroll bar of the Transcript window to view the full message or event log.

If a branch of an element is locked, rather than the element itself, you can relocate the element along with the branch. However, the relocated branch is no longer locked.

Symbolic links to a hijacked file appear in the clearviewupdate hijacked file list along with the file itself. As a result, multiple entries in the hijacked list refer to the same file.

When a file in an xcleardiff pane is rendered to a HTML browser, the HTML browser may not be able to display the file if the browser is running on a different host than xcleardiff. This situation occurs when xcleardiff does not generate a pathname to the file that is accessible from the host on which the Web browser is running.

Workaround: Run xcleardiff on the machine where the HTML browser is running.

Attempting to describe files whose names have shell special characters (for example, *) or spaces from the graphical interface may fail with a file not found error.

For example, the following describe command fails because it treats the file name as two separate names:

cleartool describe –graphical “my file“

Web clients that use Netscape Navigator may see an error message similar to the following in the Web server logs:

File does not exist: /usr/atria/web/applets/com/ms/security/PermissionID.class
File does not exist: /usr/atria/web/applets/com/ms/security/PolicyEngine.class  

These error messages are harmless and can be ignored.

When entering a version identifier as an advanced version selector in the Welcome to Merge Manager page, you must use forward slashes (/) if the Web server is running on UNIX. If the Web server is running on Windows, you may use either / or \.

You may see an error message about data code pages if you use the ClearCase LT–ClearQuest integration. The error message appears when you enter data into ClearCase LT using characters that are incompatible with the set of characters that a ClearQuest database accepts. If you see such error messages, consult with your ClearQuest administrator or systems administrator to resolve the character set incompatibility.

The attribute type real does not work correctly in an environment of both UNIX and Windows systems. In such environments, VOBs may hold values that originate from both Windows and UNIX. Values orginating from UNIX systems appear incorrect to Windows clients, and those originating from Windows appear incorrect to UNIX clients.

If two checkin operations are run simultaneously on an element and a branched sibling that share the same cleartext container, one of the checkin operations may fail. To correct the problem, perform the checkin again.

If xclearcase is not started in a snapshot view directory, an attempt to open a file in a VOB fails. To avoid the problem, invoke xclearcase from within a snapshot view directory.

The Create VOB wizard in clearvobadmin does not support the creation of component VOBs. To create a component VOB using clearvobadmin, use the mkcomp command after creating it using the wizard.

Using a UCM project that is enabled for ClearQuest may leave activities that are mastered at remote sites unlinked to the ClearQuest database. To link the unlinked activities, use the following procedure:

Conversely, disabling a UCM project from ClearQuest may leave activities that are mastered at remote sites still linked to the ClearQuest database. To unlink the linked activities, use the following procedure:

A problem has been detected storing text files in ClearCase under certain conditions. If you edit a new text file in VS.NET and check it in, the contents are stored normally. However, if you subsequently check out, modify, and check the file back in, binary data is inserted into the file.

The problem has been detected in text files that were edited using the native VS.NET source code editor, and saved to a dynamic view. The systems on which the problem was detected used a remote dynamic view UNIX server running Samba 2.0.7 for interoperability. The problem has not been detected under the following conditions:

The documentation for the ClearCase–DDTs and ClearCase–FrameMaker integrations contain incorrect references to the term atria.

If you use clearprojexp to create a single-stream project, the GUI does not recognize the project as a single-stream project until you either refresh the view or exit the GUI and restart it. Until you refresh the view or exit and restart the GUI, a user can create a child stream in the integration stream of the project. This problem only occurs in the application instance that created the single-stream project.

On platforms that use the Japanese locale, you might encounter the following problems:

You cannot use the clearexport_pvcs command to export PVCS data from a path of which any component includes the Japanese character 0x5c. The PVCS commands required for export fail in this configuration. As a workaround, rename the file or directory that includes the 0x5c character.

The mkbl –activities operation, whether invoked as a command or through a GUI, fails in an environment in which the VOB server is running Version 2003.06.00, clients are running Version 2002.05.00 and Version 4, and the following scenario takes place:

As a workaround, use the mkbl operation without specifying activities in this situation. You can then use mkbl –activities, specifying new activities.

In the UCM-ClearQuest integration, there is a new Contributors operation that may be performed on a UCMUtilityActivity type record, which represents an integration activity. This operation displays the activities or baselines that contributed to the change set of this integration activity. The contributing activities or baselines are concatenated as a string, using | as the delimiter. In other words, the string is displayed in the form, activity|activity|activity. The string is not readable when the list of contributing activities or baselines is long because it does not wrap within the window.

The command cleartool describe –graphical activity-selector does not work.

When you specify a cleartool command alias such as ci and co as the argument to cleartool man –graphical, the command fails with an error like No such file or directory. As a workaround, use the full command name, such as checkin and checkout, as the argument.

The New option on the checkout common dialog submits a new ClearQuest record, but does not set that new record to the current view context and use it for the current checkout. As a workaround, use theClearCase Properties button or use ClearQuest to transition the record to the Active state.

Creating a new ClearQuest activity using the clearprojexp or xclearcase commands can fail silently. To determine what failed, use the command cqtool submit –gui. The same failure can occur with the Properties button for ClearQuest–enabled activities. In this case, use the command cqtool find_record –gui to determine the cause.

On any host where the ClearCase LT scheduler runs a job on an hourly schedule, the albd_server will fail during the hour before the transition from standard time to daylight saving time . The failure will stop all ClearCase LT operations on the host. Note that the default set of scheduled jobs does not include any jobs that run hourly.