This file contains descriptions of noteworthy problems found in and not yet resolved in ClearCase LT software running on Windows platforms.
NOTE : The problem descriptions are stored in a change request system keyed to ID numbers. This document lists the numbers, each of which includes a CMBU prefix. The former five-digit number appears in parentheses.
The following are the known problems in ClearCase LT software.
The Print Preview menu item was temporarily removed because it was not functioning properly.
If you have existing Visual C++ projects in ClearCase LT, then you must manually rename the elements in the VOB that correspond to Visual C++ project file names to have the case-correct names. For example:
cleartool checkout .
cleartool mv foobar FooBar
cleartool mv
...
cleartool checkin .
New projects created in a snapshot view require no such renaming to work properly.
When the Windows 95 power management feature activates and switches the disk drive to low-power mode, ClearCase LT shortcut menus (for objects below the level of a view's root directory) and cleartool commands become unavailable.
Workaround : Shut down and restart the machine. Or, to prevent ClearCase LT commands from becoming unavailable on a Windows 95 host, turn off power management:
If you change the setting of CCFS in the Options tab of the ClearCase Control Panel program, you must shutdown and restart ClearCase before the change takes effect. (You can shutdown and startup ClearCase using the Services Startup tab in the ClearCase Control Panel program.)
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. An imported baseline is one that you create by importing a labeled set of versions from a VOB.
When a ClearCase activity in a ClearQuest-enabled project is linked to a ClearQuest record, the system sets the Name of the ClearCase activity to match the ClearQuest record's ID. This allows users to access the corresponding activity when they are working on a defect by using the current defect number. For example, they can use the command
cleartool setactivity ClearQuest-record-ID
Rational recommends that users not change the name of a ClearCase activity, although ClearCase LT does not prevent that. If users change an activity name, they are no longer able to 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 users change this field from within either ClearCase LT 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, it simply 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 LT generates during deliver operations.
If you attempt to add a large number of files to source control from within the Windows Explorer, the operation fails. To add a large number of files to source control, use the cleartool mkelem command instead.
There is a bug associated with taskpads in the Microsoft Management Console, version 1.1 and 1.2, which causes problems in the ClearCase Administration Console such as the following:
Select the All VOBs or All Views node from the navigation bar of the Administration Console. The program displays the associated taskpad. Now select a VOB or view tag from the taskpad list, and then select Manage storage . After the storage for that node has been successfully displayed, select the MMC "back" navigation arrow to return to and display the previously selected taskpad. Note that 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
By default, views for Web interface users are created under the host data directory for ClearCase LT ( ccase-home-dir \var). If ClearCase LT is deinstalled, the view directories are deleted, but the views remain registered. To avoid leaving entries for nonexistent views in the ClearCase registry, do one of the following:
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.
If you delete a view while the Properties page of the view is open, and then attempt to modify the view properties, the Administration Console crashes.
By default, ClearCase LT 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.
The XML Diff Merge tool displays characters correctly only if they can be represented by a single 8-bit byte. Characters that require two or more bytes, such as UTF-16 characters and some UTF-8 characters, do not display correctly. Although XML Diff Merge accepts XML input in any of four encodings (ASCII, ISO-8859, UTF-8, UTF-16), the merged output file is always encoded in UTF-8. Therefore, we recommend using only ASCII or UTF-8 encodings for XML elements that may be merged.
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 giving files names that are identical to the names assigned to basic system elements.
We recommend that you not initiate an Add to Source Control operation from the ClearCase LT 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.
When merging XML files, if one contributor version has an XML declaration node, and one or more contributors do not have a declaration node, other nodes between the declaration node and the `root' node can go missing.
To work around this problem, make sure all versions contain an XML declaration node. An example of an XML declaration node is as follows:
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:
After displaying the above error, ClearCase LT crashes.
Therefore, we recommend that you not use the above procedure to open a second ClearQuest form.
The Microsoft Management Console (MMC), and thus the ClearCase Administration Console, depend on the installation of Internet Explorer (IE) 4.0 or later. In the absence of IE 4, certain ClearCase LT features such as the Web site snapin and the view and VOB taskpads are not available, and the MMC framework in general may behave unpredictably. For example, invoking Help from the console (which is implemented using HTML Help) may cause the console to crash if IE 4 is not available. Additionally, in the absence of IE 4, the MMC menu bar and toolbars may not be available.
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 LT 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 during the time the system is in Hibernate mode. Therefore, the client ClearCase LT applications are likely to return errors when a user attempts to use them after the machine 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.
Due to a problem in earlier versions of Windows, the Date/Time control used in the Settings page of the Job Properties sheet may sometimes toggle inappropriately from PM to AM. The Job Properties sheet is part of the new Job Scheduler available through the ClearCase Administration Console .
If the current time is in the PM and the user types in a new time, rather than using the arrow keys on the keyboard or the spin control on the Date/Time control to set the time, the AM/PM field switches to AM.
This problem appears to be fixed in the latest version of Internet Explorer 5.0.
If, in a UCM view, you check out or check in an element from a VOB which 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 which 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 : Simply select the activity, it will be ignored.
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:
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:
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 PowerBuilder integration with ClearCase LT software, if you select an object from the public directory and click Source > Register , the integration displays a dialog box where you enter the name of the .PBL library. If you enter the name of a .PBL library that does not exist in the archive directory, the integration creates a new .PBL library and adds it to source control in the archive directory. If you attempt to check out the same object from the public directory by clicking Source > Check Out , and you specify a different .PBL name, the integration fails with an "error5" message. To work around this problem, be sure to enter the exact name of the target .PBL when you check out an object.
There is a known error that occurs when canceling an uncheckout confirmation dialog. It causes Adobe FrameMaker to hang.
In a Visual Basic version 6.0 project that is part of a Visual Basic Group, when you check out a .FRM file (with a .FRX file), ClearCase LT does not check out the associated .FRX file automatically. This behavior may cause synchronization problems. When working with a Visual Basic 6.0 project that is part of a Visual Basic Group, be sure to check out both the .FRM and .FRX files.
When you open a Visual Basic 6.0 project that is checked in, the integration displays the following error message: "Failed to update project location information in the host application". The integration displays this message because the Visual Basic project file is not checked out and the project location information cannot be updated. To avoid this message, check out the project file and then open the project. If you choose to check out the project file in advance, you may safely ignore this message.
The Diff Merge tool may not display multibyte characters correctly.
The output of most cleartool commands that display date information uses an invariant format that ignores regional standards.
When running clearexport_cvs , the -A option has no effect if -r has not been specified also.
If you install Windows 2000 on a machine that currently runs Windows NT with the ClearCase LT-Visual Studio integration, and you re-install ClearCase LT software, the Visual C++ 6.0 Addin toolbar for the ClearCase LT integration contains five Version Tree buttons. All five buttons start the Version Tree Browser. To correct the problem, remove the ClearCase LT toolbar and then re-add it:
When the ClearCase LT Web server running on Windows logs in a client, it sets the primary group to the designated primary group in the client user's domain account. In ClearCase LT software, you cannot override this group setting. As a result, sites that use domain mapping to allow user accounts in multiple domains to share VOBs cannot access those VOBs through the ClearCase LT Web Interface.
In the UCM-ClearQuest integration, if you change the name of the ClearQuest record type after activities have been linked to ClearQuest records of that record type, the integration displays an error message when you try to set one of those activities in a view. To change the name of a record type, do so before any activities are linked to records of that record type.
The Server Logs node of the Clearcase Administration Console may display the names of several logfiles that never have any content on a ClearCase LT Server. These logfiles include:
msadm
promote
rgy_backup
shipping
sync_export
sync_import
ws_helper
On Windows NT, mounting VOBs with the read-only option ( ro ) has no effect.
If you rename or delete an eclipsed file, the operation is performed only on the view private object that is eclipsing the ClearCase element.
The exception to this is when the view private file is being edited in Microsoft Word. Word maintains a lock on the file which makes it impossible for any other program to touch or operate on the file
Workaround: Close the file in Word, or use the ClearCase integration with Word.
You can install ClearCase LT software as a point product on the same machine on which you install a Rational Suite. If you later uninstall the Rational Suite, the icon for ClearCase LT software is removed from the desktop, but the product is not uninstalled. The ClearCase LT program is left on the computer as is its reference in Start > Programs . The icon should not be removed, because ClearCase LT software must be uninstalled separately. As a workaround, you can manually put the icon for the ClearCase LT Explorer on the desktop.
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).
The UCM shortcut pane always appears in the ClearCase Explorer. You cannot set the Explorer to not display UCM. If you remove all shortcuts from the UCM section, UCM disappears. However, the system does not save the configuration. After you close the Explorer and reopen it, the UCM shortcut pane appears again.
Patch information for ClearCase releases might not be correctly displayed by cleartool lsclients .
For users who belong to a user group that is not allowed to see the ClearQuest record, the following error message appears when they specify the record while performing an Add to Source Control , Checkout , or Checkin New operation from a ClearCase GUI:
Error! Execution of a hook failure during the action
Submit.
It was the ACTION_COMMIT hook attached to the BaseCMActivity
`cqms0000111".
The reason for the failure was:
IDispatch error #14094
UCM_Project 33554485 does not exist or has already been deleted.
Table 1 lists significant problems in previous ClearCase LT releases that are fixed in this release.
Table 2 lists the status of problems reported in previous releases.