When your build script builds over a target without first removing it, the script must retain the permissions of the built-over DO. Your view maintains these permissions correctly, but the data container created by the MVFS gets new, potentially different permissions. As a result, subsequent attempts to build over the target may fail.

You cannot copy a read-only folder to the MVFS. After copying the read-only folder into the MVFS, it is protected against changes and the subsequent copying of any files or subfolders into it fails.

Workaround: There are two possible workarounds to this problem:

If you are using a version of InstallShield earlier than 5.1 and your InstallShield build includes a checked-out header file, InstallShield opens the file for read/write, which causes the MVFS to erroneously turn the include file into a DO.

Workaround: Upgrade to a current version of InstallShield.

If you change the setting of the Enable automatic mounting of NFS storage directories option in the ClearCase Control Panel after starting any remote NFS views or mounting any remote NFS VOBs, you must shut down and restart your computer. Otherwise, accessing MVFS files on remote NFS storage directories will produce incorrect function errors and opensendirp error messages in the MVFS logs.

In the current release, when working with nested and universal groups, a spurious failure may be reported when testing whether the clearcase_albd user account is in the ClearCase Administrators Group. The failure should be ignored.

Also, the setup will not create an account in a domain that has a transitive trust with the current domain.

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.

When a ClearCase activity in a ClearQuest-enabled project is linked to a ClearQuest record, the Name of the ClearCase activity is set to match the ClearQuest record's ID. This allows you to access the corresponding activity when you are working on a defect by using the current defect number. For example, you can use the command

cleartool setactivity ClearQuest-record-ID 

We recommend that you do not change the name of a ClearCase activity, although ClearCase does not prevent that. If you change an activity name, you cannot use the setactivity command as illustrated above.

Note that the Headline field for a ClearCase activity is synchronized with the corresponding field in a ClearQuest record. That is, if you change this field from within either ClearCase or ClearQuest, the corresponding field in the ClearQuest record or ClearCase activity is modified as well.

If a branch is removed from within a snapshot view, any loaded elements from that branch should remain in the snapshot view. However, when trying to list such an element, the program displays the error

cleartool: Error: Pathname is not within a VOB

The error is generated when attempting to list an element if the branched version of the element was previously selected by the snapshot view, but the branch has since been removed. Note that the element still exists in the VOB and the view, but cannot be listed by cleartool ls.

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.

If you attempt to add a large number of files to source control from within Windows Explorer, the operation fails. To add a large number of files to source control, use the cleartool mkelem command instead.

The Print to file option of applications such as Microsoft Word does not work for an MVFS file. Attempting to print to file within the MVFS may result in the error access denied or the application may appear to hang as it continues to try to write the file. The problem is that the mechanism used for this function uses an identity that does not have the proper credentials for the MVFS to be able to validate it. The workaround is to print the file to a file outside the MVFS (such as a local or network drive) and then copy it into the MVFS from there.

There is a bug associated with taskpads in the Microsoft Management Console, version 1.1 and 1.2, that causes problems in the ClearCase Administration Console. The problem occurs when you follow this sequence of steps:

The taskpad list is blank.

Workaround: Use either of the following methods to work around the problem:

Note that with MMC 1.1, resizing the console window refreshes the list; resizing has no effect in MMC 1.2

The cleartool describe command lists predefined attributes for some objects. This output is likely to change at a future release. Specifically, settings that represent UCM information are likely to be removed or replaced with a more abstract representation.

By default, ClearCase software does not create a new version of a file that is identical to its immediate predecessor. When you attempt to check in a .frm file that is identical to the checked in version, the integration does not check it in. However, if the .frm file has an associated .frx file, the integration checks in the .frx file as a read-only file. To avoid this problem, set the option to allow identical checkins.

Files with names such as AUX.ext, CON.ext, PRN.ext, or NUL.ext, where ext is any file extension, can be loaded into a snapshot view, but cannot be unloaded from the view or deleted from the system. This makes it impossible to delete parent directories of such files as well. We recommend that you avoid using files names that are identical to the names assigned to basic system elements.

Workaround: Enter the following command:

del \\?\drive:path 

We recommend that you not initiate an Add to Source Control operation from the ClearCase menu that appears when you right-click in the SaveAs dialog in MS Word. This may cause your Word application to terminate abruptly, and could possibly cause data loss.

The UCM/ClearQuest integration does not prevent you from opening a ClearQuest form, then going to the form's UnifiedChangeManagement page, then using the shortcut menu in the change set to open a ClearCase dialog box, and then selecting Activity Properties, which opens a second ClearQuest form.

However, if you follow the above steps, the second ClearQuest form does not function correctly. In particular:

Therefore, we recommend that you not use the above procedure to open a second ClearQuest form.

The font used for text and captions in the History Browser is 6 point type by default. This point size produces difficult-to-read output in the History Browser on a Japanese language system.

Workaround: To enlarge the font, click View>Options>Display>Fonts and select a larger font.

Windows 2000 includes a Hibernate feature that allows the state of the current running system to be saved and restored quickly later on. Active ClearCase processes, as well as processes that have the ClearCase Network Provider loaded, may have TCP connections to servers on remote machines; such connections are likely to be closed by the servers while the system is in Hibernate mode. Therefore, the ClearCase client applications are likely to return errors when a user attempts to use them after the computer has been brought back from Hibernate mode.

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.

In Visual Basic when you attempt to add a project to ClearCase by clicking Tools>ClearCase>Add Files to ClearCase, the operation fails if the VOB in which the Visual Basic project resides has a trigger that requires users to enter a comment when checking in files. The Visual Basic IDE does not supply the comment that you enter in the Add to Source Control dialog box to the trigger.

To work around this problem, use ClearCase Explorer to add the project to source control. After you add the project to source control, checkin and checkout operations complete successfully from within the Visual Basic IDE.

When adjusting MVFS caches as described in Administrator's Guide, take care not to use too much of your kernel memory. If the cache size settings are too large, you may exhaust kernel memory, which can cause your system to hang or crash. The upper limits for cache sizes depend on the amount of memory in the system, the particular system configuration, and the nature of the work being performed on the system. A ClearCase administrator should monitor system memory use while increasing MVFS cache sizes.

Occasionally, when merging a file with Merge Manager, the combo box that indicates the view to be merged from, displays two instances of each available dynamic view. In this situation, you can click either dynamic view to select it. The symptom is not known to cause any problems.

Using the UCM-ClearQuest integration, you can customize the Check Before Deliver ClearQuest Visual Basic policy script. However, if the script as customized contains an error that causes the Visual Basic interpreter to display an error exception, the Deliver dialog box reports this error like this:

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

It does not report the actual error exception text which would enable the user to diagnose the problem script

Workaround: To see the error exception text, use the cleartool deliver command.

Using the UCM/ClearQuest integration, if you upgrade a ClearQuest user database to a new schema revision, in order to see the change on a client machine which was connected to that user database, you must do the following on the client machine:

On Windows NT or Windows 2000:

On Windows 98:

When using the UCM/ClearQuest integration, the list of records displayed in the dropdown list on the Add To Source, Check Out and Check In dialog boxes is generated by running the UCMCustomQuery1 query, which can be customized. (Note that in order to see the effect of your changes, you must use the File>Save menu item to save the query edits.)

However, if you copied the Public Queries UCMCustomQuery1 query into your Personal Queries folder and edited it there, the changes are not immediately seen. To see your changes, you must stop the integration server process:

On Windows NT or Windows 2000:

On Windows 98:

After stopping the process on your computer, open the dialog box again. Further edits to /PersonalQueries/UCMCustomQuery1 show up automatically without having to shut down the process again.

While displaying a view private file in the ClearCase Administrator's or Host Console, resizing its column headers or displaying the shortcut menu causes the Refresh toolbar button to be hidden. If this happens, you can access the Refresh action by using the Action menu pull-down, or from the shortcut menu of the view private file's display.

When using the ClearCase integration with Microsoft Visual Basic, do not use the 'browse' button in the 'share' dialog, or you may cause the application to hang. Instead, either supply a complete path to the share dialog using the edit box, or avoid using the dialog at all.

If a user's web view is deleted from outside the web interface (e.g. with a "cleartool rmview" command on the web server), it will no longer show up in the Select View page of the web interface, even though the corresponding view location area on the client may still exist. There is no indication that the server component of the view disappeared.

The Diff Merge tool may not display multibyte characters correctly.

Workaround:

The output of most cleartool commands that display date information uses an invariant format that ignores regional standards.

Clients using Netscape Navigator may cause error message similar to the following to appear 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.

On WIndows, running multiple instances of regsvr32 to register the same .dll in the same VOB and view may cause the machine to hang.

When running ClearCase on a simplified Chinese version of Windows, the labels on dialog boxes are clipped. This effect results from a bug in Microsoft Foundation Classes. Microsoft has no known workaround for this problem.

On Windows, clearprompt -list only displays the first 512 lines in a list of items. The remaining items are ignored.

To enable logging text to display inside an IDE, the user must set the registry key HKEY_CURRENT_USER\Software\Atria\ClearCase\CurrentVersion\SCC\DebugTrace = 1 (or = 3 for additional logging to a file). This logging mechanism works for any IDE that supports messages from an SCC provider.

A Not a VOB Object message appears if you select Add to Source Control. In this case, the SCC proceeds to add the element to source control.

There is a bug in Microsoft library, which affects a display of extended characters within cmd.exe. We know Cyrillic and German characters are affected. This problem only happens within cmd.exe when cleartool.exe is used.

Patch information for ClearCase releases may not be correctly displayed by cleartool lsclients .

Workaround: Use cleartool -ver.

Usernames that have a period in them (for example, j.doe) or a space (for example, jane Doe) will cause the ClearCase tutorials to fail. Create a username without any periods and spaces before running the ClearCase tutorials.

While you can view and manipulate UCM trigger types using the ClearCase Automation Library (CAL), you cannot currently apply these trigger types to UCM objects from CAL.

There may be situations where the original Windows version of the Base ClearCase/ClearQuest integration ("V1") fails to see the expected ClearQuest database because of outdated or incorrect description information that is maintained in the Registry. The error message that results is

"Error trying to logon to the ClearQuest database"

If this occurs do the following:.

Using a JIDL compiler from Orbacus (www.Orbacus.com) fails within MVFS on Windows NT systems , but not on Windows 2000 systems.

Workaround: Work within a snapshot view, compile outside of ClearCase, or run on a Windows 2000 system within MVFS.

Because of changes made to the MVFS to support Active Directory, users who are members of multiple groups may experience problems creating and modifying view-private files in dynamic views on Windows if they are not the view's owner.

To correct this problem, take either of the following actions:

When trying to create a VOB symbolic link with the same name as an existing link, youl get the error

Can't modify directory because it is not checked out. 
Unable to create link: "M:\path\file".

On Windows 2000, if the Diff Merge tool is already set to show the carriage return markers on the display, and those markers are turned off, the resulting display is double-spaced. This is a display problem only, and can be corrected by clicking Edit->Restart Comparison. The application will start normally on the next invocation.

The Add View Shortcut dialog may appear to be hung if the diskette drive is disconnected, as it might be on a laptop. This dialog contains a drive letter combo box which should be filled with available drive letters, as well as the drive letter that may be already connected to the view that you chose. If a diskette drive is disconnected, it may take 10 or 15 seconds to time out. During this time the application is inaccessible.

When creating a UCM integration view, the stream it will be attached to, and any existing web views for that stream, are displayed in Internet Explorer, but not in Netscape Navigator, due to limitations of the support for dynamic HTML in Navigator 4.x.

When using a dynamic view as a merge source in the ClearCase Web interface, any elements which are checked out in that view (and need merging) cause an error during the merge. The elements should be checked in (or uncheckedout, as appropriate) in the source view before merging.

On Internet Explorer and above, deliver and rebase status is indicated by incremental updates to the status text area, the transcript, and the file listing area, as data is received from the server. Because of bugs in Netscape Navigator 4 which causes the browser to crash when partially occluded, the file listing area cannot be updated incrementally (that is, changes to checkout and merge state cannot be updated incrementally). When using the ClearCase Web interface through Netscape Navigator 4, the file listing area is updated after each major phase of the deliver/rebase request has completed.

When running the Report Builder, you must have local administrator rights on the computer to be able to create reports about the state of dynamic views. Otherwise, dynamic views do not appear in the combo box list of views when you are selecting one on which to create a report. Any snapshot views created on the local system do appear on the list, whether or not you have local administrator privileges.

The UnifiedChangeManagement package has six pre-defined public queries,

Two of the above queries are used by UCM/ClearQuest integration, UCMCustomQuery1 and MyToDoList.

In UCM1.0 and UCM2.0 Package, query MyToDoList is defined as:

AND
    ucm_statetype in ('Active', 'Ready')
    Owner = '(CURRENT_USER)'

Upgrading to the UCM3.0 package requires the AMStateType 1.0 package; after applying the AMStateType 1.0 package, the field ucm_statetype no longer exists (using am_statetype instead). But since the pre-defined queries in UCM 3.0 do not reflect this change, they do not perform the expected functions.

This problem is corrected in the UCM 4.0 package shipped with ClearQuest Version 2002.05.00. To correct the problem in UCM 3.0, replace occurences of ucm_statetype with am_statetype where they appear, using the same values that were associated with the previous field name. For example, the MyToDoList query should be defined as

AND
    am_statetype in ('Active', 'Ready')
    Owner = '(CURRENT_USER)'

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 forward (/) or backward (\) slashes.)

When using the ClearCase Web interface on a Netscape 4 browser, use of the browser's Back button can cause unintended results in the Web user interface.

On Windows/NT, creating a symbolic link to the VOB root from a child directory works correctly but produces spurious error and warning messages:

cleartool: Error: Symbolic Link cycle detected for "vobname\child_directory\vobroot". 
cleartool: Error: Errors were encountered in loading "\vobname\child_directory\vobroot". 
cleartool: Warning: Trouble updating name "vobroot" in snapshot view: error detected by ClearCase subsystem.  

The output form the command indicates that the link is successfully created and is correct.

When using the XML Diff Merge tool, if the web browser pane is visible, and the user clicks either Show All Diffs or Show All Conflicts, the web browser display goes blank. The web browser pane should be unaffected.

Workaround: Click one of the contributor panes, and the web pane is refreshed.

Some applications, for example Windows Notepad on Windows 2000, may include a Byte Order Mark (BOM) when directed to save results encoded as UTF-8. If the first three bytes of an XML file are { EF BB BF } (hex), the file is UTF-8 and the 3-byte sequence is the BOM. While a BOM is mandatory for UTF-16 files, it is optional for UTF-8 files.

The XML parser used by XML Diff Merge does not recognize the UTF-8 BOM, and instead reports a syntax error. To compare or merge such files with XML Diff Merge, one of the following workarounds may be used:

In the ClearCase Web interface, when you browse to a directory that contains a symbolic link with a backslash ('\') in its link text, a Javascript error is displayed.

Workaround: Change symbolic links to use forward slashes instead. (Forward slashes work with both Windows and UNIX clients.)