This file explains the status of noteworthy problems in Rational ClearCase Version 2003.06.00.
This file consists of the following sections:
Note: During this release, the ClearCase Product Family development group was in the process of changing from one database schema for software change requests to another. Depending on the state of a change request at the time of publication of this document, the change request may be identified by its old CMBU ID, its new RATLC ID, or by both IDs.
The following are known problems in ClearCase Version 2003.06.00.
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 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.
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.
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
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.
The cleartool describe command lists predefined attributes for some objects. This output is likely to change in a future release. Specifically, settings that represent UCM information are likely to be removed or replaced with a more abstract representation.
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 command, del \\?\drive:path
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.
The UCM-ClearQuest integration does not prevent you from opening a ClearQuest form, then going to the form's UnifiedChangeManagement page, using the shortcut menu in the change set to open a ClearCase dialog box, and selecting Activity Properties, which opens a second ClearQuest form.
However, if you follow this sequence of steps, the second ClearQuest form does not function correctly. In particular:
After displaying this error, ClearCase crashes.
Therefore, we recommend that you not use this procedure to open a second ClearQuest form.
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.
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:
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, 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
When using the UCM/ClearQuest integration, the list of records on the list in the Add To Source, Check Out and Check In dialog boxes is generated by running the UCMCustomQuery1 query, which can be customized. (Note that to see the effect of your changes, you must click File > Save 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
After stopping the process on your computer, open the dialog box again. Further edits to /PersonalQueries/UCMCustomQuery1 appear without your having to shut down the process again.
When you display a view-private file in the ClearCase Administrator 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 command on the Action menu, or on the shortcut menu from the view-private file.
When using the ClearCase integration with Microsoft Visual Basic, do not use the Browse button in the Share dialog box, which may cause the application to hang. Instead, either supply a complete path to the Share dialog box using the Edit box or avoid using the dialog box.
If a user's Web view is deleted from outside the Web interface (for example, with a cleartool rmview command on the Web server), it no longer appears 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.
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.
On Windows 2000, if the Diff Merge tool is set to show the carriage return markers on the display and those markers are turned off, the resulting display is double-spaced. This problem can be corrected by clicking Edit > Restart Comparison. The application will start normally on the next invocation.
The Add View Shortcut dialog box may appear to hang if the diskette drive is disconnected, as it may be on a laptop. This dialog box contains a drive letter combo box that should list 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 using a dynamic view as a merge source in the ClearCase Web interface, any elements that are checked out in that view (and need merging) cause an error during the merge. The elements should be checked in (or their checkouts cancelled, as appropriate) in the source view before merging.
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 \.
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 of 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 you click 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 to refresh the Web pane.
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:
The install program does not verify that the installation destination directory is a valid Windows directory. If an invalid directory name is entered, the install may complete, but the installed product is not likely work correctly.
Release area pathnames should not contain multibyte characters.
In the Site Preparation Tool, you must always use the mouse to click the Next and Back buttons. Alternatively, you may go to specific pages by clicking the list control. The Site Preparation Tool does not support the use of keyboard accelerator keys. Alt+N is not equivalent to the Next button, and Alt+B is not equivalent to Back. If you use these key sequences, Site Preparation Tool will advance to the next "dialog resource" instead of the next "page," and this results in an incorrect display. If you type Alt+N (Next) inadvertantly, you can type Alt+B (Back) to go back to the original page. No damage or corruption will occur if you do this and you can proceed with the install.
When WebSphere Studio refactors Java package names that are under ClearCase control, it does not rename the package directory, but instead deletes the old location and creates new files in the new location. Consequently, the version history of the Java package is lost. In addition, you are prompted to add the package to source control.
There is an extra welcome screen during startup.
If a rebase operation fails with the message No permission to perform operation “remove hyperlink” and you are using a replicated VOB, the baseline hyperlinks associated with your current stream may not be mastered by your current replica. The failure occurs because the chmaster –stream command does not change mastership for baseline hyperlinks associated with that stream.
Workaround: Use cleartool describe to find the hyperlinks, and then use chmaster to change their mastership to the appropriate replica. For example:
CC Doctor sometimes reports a spurious region-checking failure with the message, Nonexistent ClearCase Region or Regions: Region " " unknown ... Ignore the error. To confirm the existence of region, use the lsregion command.
In the integration with PowerBuilder versions 6, 7, and 8, importing PBLs sometimes fails. The workaround is to use third-party solutions or upgrade to PowerBuilder version 9. PowerBuilder 9 can determine whether PBLs need to be changed, and the PowerBuilder 9 integration does not require versioning PBLs. Instead, you can write Orca Utility scripts to rebuild targets.
You may see an error message about data code pages if you use the ClearCase–ClearQuest integration. The error message appears when you enter data into ClearCase 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.
When installing a Suite with the optional ClearQuest Shipping Server feature enabled, ClearCase LT is disabled because it conflicts with this ClearCase feature. In this case, the Site Preparation Tool—or, if you are installing the software, the configuration screens—incorrectly requires you to specify a name for the ClearCase LT server. As a workaround, type any string as the name of the server. The server name will be ignored because ClearCase LT will not be installed in any case.
XDE versions 2002.05.20 and earlier do not operate correctly when ClearCase starts a merge operation. The merge operation attempts to call the XDE type manager, which fails. To avoid the problem, we recommend upgrading to a newer version of XDE but if that is not possible, use the following procedure to correct the problem:
_xde construct_version ..\..\bin\bdtm.exe _xde create_branch ..\..\bin\bdtm.exe _xde create_element ..\..\bin\bdtm.exe _xde create_version ..\..\bin\bdtm.exe _xde delete_branches_versions ..\..\bin\bdtm.exe _xde compare HKEY_LOCAL_MACHINE\SOFTWARE\Rational Software\XDE\TypeManager _xde xcompare HKEY_LOCAL_MACHINE\SOFTWARE\Rational Software\XDE\TypeManager _xde merge HKEY_LOCAL_MACHINE\SOFTWARE\Rational Software\XDE\TypeManager _xde xmerge HKEY_LOCAL_MACHINE\SOFTWARE\Rational Software\XDE\TypeManager _xde annotate ..\..\bin\bdtm.exe _xde get_cont_info ..\..\bin\bdtm.exe
The VS.NET Solution Explorer displays a hijacked file with the lock icon, indicating that the file is under version control, but gives no indication that the file is hijacked. To verify the state of an element, use ClearCase to check its properties.
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.
When run in interactive mode, cleartool does not handle element names correctly if they contain embedded spaces.
To deliver a single baseline, the deliver operation GUI requires you to select each baseline that is not to be delivered and click Remove. There is no workaround.
On the Change Set tab of an activity's propert sheet, you cannot check in or cancel checkins of multiple versions of the change set at the same time; you can only checkin one version or cancel the checkin of one version at a time. However, you can right-click the activity in the Project Explorer and select Checkin All from its shortcut menu to check in all versions associated with the activity.
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:
On the MVFS Settings dialog, two fields labeled Maximum number of mnodes... are loaded based on the selection in the Scaling factor combo box. If you specify a nondefault value in either of these fields and then redisplay them, the value is overwritten by the default value. As a workaround, you can either use the default values or avoid displaying MVFS Settings after you have specified a nondefault value.
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.
During a custom install on Windows .NET Enterprise Server RC2, the configuration window sometimes appears below the install window, which gives the impression that the installer is hung. The Configure application will appear in the task bar; click the icon to move the application to the foreground.
The required disk space reported by the install program is unreliable. For accurate information, see the Installation Guide for your product.
If you use the UCM-ClearQuest integration connected to a user database in Microsoft Access 2000, you may encounter an error when you remove an activity record using the native ClearQuest client. If the record is associated with an activity that is set in a view, a debugger window incorrectly opens for clearquest.exe. A message correctly states that the activity cannot be removed because it is set in a view.
To recover, close the debugger windows. To remove the activity record, use ClearCase to unset the activity in the view and retry the operation.
Setting the environment variables PERL5LIB or PERLLIB in the environment from which ClearCase processes are run may result in run-time errors having to do with the ClearCase Perl interpreter finding the wrong versions of Perl modules.
You can create and edit multiple configuration documents during a single run of the Site Preparation Tool. The Completion component functions correctly on the first document; however, if you attempt to create or edit additional documents, the Completion component will be missing. As a workaround, work on only one document per invocation of the Site Preparation Tool.
When focus is within an edit control, an attempt to creat a new document can result in a crash. To create a new document (using File > New or File > Open), ensure that the focus is not within an edit control by clicking elsewhere, for example, on a tree node or button.
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.
If you copy a WebSphere Application Developer 4 Java Project from one VOB to another without adding the file to source control, and you then import the project into WebSphere Application Developer 5 by clicking the Import > Existing WebSphere Studio 4.x ClearCase Project into Workspace option in WebSphere Studio, the Java nature of the project is lost.
When installing from a remote release area on a Windows 2000 server with the application-mode Windows Terminal Service enabled, the install may fail silently. This becomes apparent when UseDLL failures occur. The failures are logged in the file rational_install.log and you can search for them using the following command:
%windir%\system32\find.exe /i “fail” %TEMP%\rational_install.log
Such failures mean that the install failed. For example, ACLs on the installed directory may not be set. As a workaround, avoid installing the product in this manner.
You cannot compare HTML files—for example, by using diff—if the install directory contains the character 5c in the trail byte. This problem affects Japanese language installations.
The creds command does not issue a warning when a user is not a member of the domain group named by the user's CLEARCASE_PRIMARY_GROUP environment variable.
JBuilder project contents are not enabled for ClearCase after you click Add to Source Control. As a workaround, when you create a new resource in JBuilder, first save the resource and then click Refresh Status.
The install log that is written to the user's temp directory may be lost on WTS systems that remove that directory when the system is rebooted.
There may be a problem when certain file and directory pathnames are read by the Site Preparation Tool. Some data fields may contain multiple lines of text. Each line is terminated with an EOL marker, which is <CR><NL> on Windows. For storage in the output site defaults file, these EOL markers are converted to the character sequence \n. If a pathname happens to contain the character sequence \n, it is converted to a Windows EOL marker. For example, a path like C:\one\new\thing.ini would be converted to C:\one<CR><NL>ew\thing.ini.
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.
In the ClearCase–VS.NET integration, you click Tools > Options to modify IDE settings. However, the Help button on the Options page fails to access its Help topic. The correct Help topic for this page, Rational ClearCase Options Window, is available in Help for the ClearCase Integration with VS.NET. You can access it from the topic, Setting Options for the ClearCase VS.NET Integration.
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.
CC Doctor may fail because of an incorrect registration after you cancel an install that is in progress. To rectify the situation, use regsvr32 to register ccdoc.dll manually in such cases.
The ClearCase Explorer icon persists after you uninstall the product. After completing the deinstall, you can remove the icon manually.
The install program sometimes fails with the error 1607: Unable to install InstallShield Scripting Runtime. Consult http://www.installshield.com for information about resolving this problem.
The UNIX mapping domain in the ClearCase control panel is labeled "Use this domain to map UNIX user and group names." The installation of a ClearCase server may leave the UNIX mapping domain blank. The UNIX mapping domain is needed only for configurations that support UNIX snapshot views accessing Windows VOBs. If this item is needed for your configuration and is blank, you may receive error messages indicating that support for UNIX clients was disabled. To fix the problem, select an appropriate domain from the Options tab of the ClearCase control panel.
Rational recommends that you avoid configuring any one host to run the Rational Shipping Server for both ClearCase and ClearQuest, because de-installing either product from such a host will remove the Shipping Server that is used by both products and render the remaining product inoperable. If you must install both ClearCase MultiSite and ClearQuest with the Rational Shipping Server on the same host, ensure that you do the following:
Note: Administrators should be sure that site configuration files for typical host systems do not specify installation of the Rational Shipping Server. Any attempt to install ClearCase on a host where ClearQuest and the Rational Shipping Server is already installed will fail.
When you specify a cleartool command alias such as ci and co as the argument to cleartool man, 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.
License key information is not initialized when configuring a system after deinstalling an earlier release. To install without the keys, temporarily specify a license server while entering configuration information. After installing the software, enter the license keys in the ClearCase control panel. They are retained in the registry key HKLM\Software\Atria\ClearCase\CurrentVersion\LicenseKeys.
When there are spaces in the path to a release area, a shortcut created by the Site Preparation Tool to a site defaults file in that directory fails. To work around this problem, use one of the following methods:
Merge operations can incorrectly allow EOL markers (newlines) in a resolved merge region to be deleted, which can result in data corruption. EOL deletion can occur in the following circumstances:
If you inadvertantly delete a newline preceding or following the resolved region, restart the merge.
In the diff-merge GUI, graphics in the left margin of the contributor that has focus sometimes become desynchronized with the corresponding text. To force the margin to be redrawn, scroll the contributor or move a pane splitter.
After rebooting a system on which you have run a silent install of the ClearCase server, ClearCase Doctor and the Server Storage Wizard are not invoked as they should be. As a workaround, invoke them manually.
On any host where the ClearCase 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 operations on the host. Note that the default set of scheduled jobs does not include any jobs that run hourly.
If you specify -blank_ignore and -graphical when invoking a diff or merge operation from the command line, the GUI crashes. As a workaround, do not specify -blank_ignore on the command line. When the GUI is displayed, use the toolbar to specify that blanks are to be ignored.
If you are modifying the installation of any product available from the Rational Setup Wizard, a fatal error occurs when you click the Space button in the Custom Setup page. To prevent the Setup Wizard from failing, do not click the Space button.
This release incorporates all service releases through 2003a.
Table 1.1 lists significant problems in previous ClearCase releases that are fixed in this release.
Table 1.1. ClearCase Problems Fixed in This Release
Table 1.2 lists the status of problems reported in previous releases.
Table 1.2. Disposition of Problems in Previous ClearCase Releases
Copyright© 2003 Rational Software. All Rights Reserved.