This file contains descriptions of noteworthy problems found in and not yet resolved in ClearCase LT software running on UNIX 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.
xclearcase may fail with grp files using the Shift-JIS (SJIS) Japanese character encoding.
xclearcase does not correctly discriminate between the second byte of some shift JIS characters (which are in hexadecimal code 0x5c) and the ASCII code for backslash (\).
On a host that has a Link-Only installation, you cannot tell which products have been installed by looking in ccase-home-dir. By definition, the Link-Only installation model provides access to all files in the networkwide release area, even if the product to which the files belong is not installed. In other words, it may appear that you can run a certain program when, in fact, you cannot because the software has not been installed.
On machines configured with a per-process data size limit of 16 MB, certain applications, including some of the new GUI programs and some HyperHelp online help files, may run out of memory and display errors.
In addition, the new GUI programs may not work with some older versions of X Windows/CDE.
Commands on the Edit menu, as well as the Display Search Criteria and Display Element Log commands on the View menu, are not available when running the Merge Manager.
When you use xclearmrgman to merge elements, the tool does not automatically prompt you to do a graphical merge. It also does not ask users if they want to look for other items to merge. Instead, elements must be selected and merged manually.
When you start the Merge Manager, it queries existing views and VOBs. If someone adds a VOB or makes changes to a VOB (for example, adds an element), the Find Wizard in the Merge Manager is not aware of the changes unless you exit and restart the Merge Manager.
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.
If you select the Add all command in the Merge Manager window titled Select the elements that you want to consider for merge, the resulting window, titled Where do you want to merge from, displays incorrect branch and label data. In this case, the list displayed in the second window is actually the last batch of branches looked up by the Merge Manager, rather than the actual list of branches available to be merged from.
Using the Add command rather than the Add all command to add elements updates the branch and label lists correctly.
Merge Manager Merge Type data for an element is not accurate after an uncheckout and refresh operation. To display the correct Merge Type data, you must restart the Merge Manager.
On some platforms, the new Merge Manager starts an xterm window to display the required ASCII data if the user clicks the Source or Destination button or the Tool >History command.
If the user then tries to resize the window before seeing the prompt "Type <CR> to exit", some of the data displayed in the window and the data is duplicated.
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.
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 source is not another VOB symbolic link.
On Linux platforms, if you use the Clear View Update GUI to check in a hijacked file element, and then try to use the GUI to display a version tree of that element, the version tree is not displayed. Instead, the tool displays the following error message:
xclearcase: Error: Invalid pathnames
The error message is displayed on the command line in the terminal window where you started Clear View Update.
Workaround: Use the command line interface tool xlsvtree to display the version tree.
On Linux platforms, if you use the Clear View Update GUI to check in a hijacked file element, and then use the GUI to select the Hijacked folder, the tool displays an empty Name field, instead of listing the name of the hijacked file that was checked in.
By default, views for Web interface users are created under the host data directory for ClearCase LT (/var/adm/atria). 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:
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.
When using the Merge Manager to merge files to a UCM-controlled branch, there is no way to set an activity. If no activity is currently set in the view, the checkout operations fail. In addition, if the wrong activity is set, the operation completes without allowing the user to confirm or cancel it.
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 pop up automatically when exception conditions have occurred during an operation. When the Transcript window is up together with the another modal dialog box, such as a properties dialog where operations can be initiated, the Transcript window does not respond to user actions. You must first close the modal dialog box before you can adjust the scroll bar of the Transcript window to view the full message or event log.
The chproject command does not let you convert a component from modifiable to read-only. This defect causes problems for project leaders who want to rebase a modifiable component in their integration stream to something other than a successor to the current baseline.
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.
When using the Merge Manager, you do not see the toolbar, even if you have set View >Toolbar, until after you use the View >Status command to display the status of an operation.
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 a single file.
When you are working in a snapshot view whose working directory is a global network path (for example, of the form /net/hostname/directory), the update -add command may fail with the message:
cleartool: Error: Unable to determine version for VOB root directory element.
Workaround: Specify your working directory using the local absolute path, for example, /usr1/smith/views/4.0_view.
There is a known error that occurs when canceling an uncheckout confirmation dialog. It causes Adobe FrameMaker to hang.
In snapshot views, the findmerge command and the Find Wizard in the Clearmrgman GUI cannot follow VOB symlinks. When you direct these operations to follow links, they generate error messages when they encounter VOB symlinks.
The first page of the Find Wizard in
the Merge Manager displays the Next button improperly. If you select Merge to a snapshot view item, the Next button appears even if no snapshot view is
selected. Clicking Next invokes an error message,
fill error
, to appear on stderr and the
wizard does not function properly. You must click Cancel and select the Find
Wizard again.
To avoid this error, choose a snapshot view (if Merge to a snapshot view is selected) before clicking Next.
On Red Hat Linux, if you select multiple files before you click the Describe command on the Report menu in the File Browser, the Describe window displays an error message:
binary operator expected
Workaround: The Describe window displays the correct information when you select one file.
When you merge elements using the Merge Manager in snapshot views, the Find Wizard does not display the branch and label information after you select your elements.
Workaround: Add the VOB root to the merge list.
For the ClearCase LT/ClearQuest integration to work, you need the printenv command in your PATH. On Solaris, printenv is located in /usr/ucb.
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 machine than xcleardiff. This situation occurs when xcleardiff does not generate a pathname to the file that is accessible from the remote machine where 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 command fails because it treats the filename as two separate names:
cleartool describe -graphical "my file "
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 information in ClearQuest records is changed from a ClearCase application, such as cleartool or the UCM Project Explorer, the ClearQuest display may not always reflect the actual contents of the database. To refresh the display, close and re-open the database from the File menu.
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 checkin comment is taken exactly from the comment text box. If the comment text box is blank, it will check in with the comment string "" (empty string).
On some UNIX platforms, mounting VOBs with the ro option works properly; that is, it prevents writes to view-private files within the VOB, but does not prevent other clients from modifying the VOB nor does it prevent changes that do not go via the MVFS, such as some cleartool operations. However, on other UNIX platforms (namely, HP-UX 11.0 mounting VOBs with the ro option prevents view-private changes to the file namespace (such as creation or deletion of view-private files) but does not prevent writes to view-private files.
The MergeTool Work Area Status Bar clips the top half off the
creating integration activity
message.
Other messages appearing on the second line of the status bar are displayed
correctly. Changing font size or resizing dialog box does not eliminate the
problem.
ClearCase view servers make anonymous accesses made by users logged in as root on remote machines. That is, the view server treats the user identity as a particular anonymous user with world access rights (known typically as user nobody). This is similar to the default behavior of NFS.
If there are multiple versions of Perl in your environment, cleartool diff operations on HTML elements may fail because of differences between Perl versions.
By setting an environment variable CLEARCASE_PERLLIB to any value, the HTML type manager ignores the value of any other PERLLIB environment variable that was set. cleartool diff operations on elements should complete successfully.
Patch information for ClearCase releases might not be correctly displayed by cleartool lsclients.
Workaround: Use cleartool -ver.
If the view already has associations with multiple replicas in the VOB family, view_sr prints an error and does not reconfigure the checkouts and view-private files. This situation may occur when a site is using an unsupported configuration in which multiple replicas in the VOB family are accessible in a single region.
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.
FlexLM installation text incorrectly suggests that this program installs ClearCase LT.
The FlexLM installation text incorrectly refers to the previous version of ClearCase LT as LT 1.0.
If you specify an installation directory that is not empty, the install utility halts the install process to avoid deleting directory contents accidentally, and displays an error message.
In the previous version of ClearCase LT, the installation deleted the directory contents without any warning.
The Rational ClearCase integration with Forte for Java is not available for Red Hat 6.2 Linux and Red Hat 7.0 Linux. This is because of a defect in Sun's Java Virtual Machine implementation that interferes with command line processing.
Table 1 lists significant problems in previous ClearCase LT releases that are fixed in this release.
Problem Number |
Description |
---|---|
#CMBU00026251 |
(#29438)merge from window displays incorrect branch list |
#CMBU00026410 |
(#29616) possible to install /usr/atria when this is a mount point |
#CMBU00026917 |
(#30193)install fails if /etc/nsswitch.conf has services set to files |
#CMBU00038844 |
clearmrgman does not find elements that needed merges. |
#CMBU00040434 |
xclearcase fails on dual-headed Solaris machines |
#CMBU00042349 |
z_type managersbroken for filenames with embedded blanks |
#CMBU00044722 |
using ClearCase Web Interface, problem overriding primary group |
#CMBU00045823 |
Attache client removes read-only attribute, even if it cannot overwrite a file |
#CMBU00045837 |
Attache 4.1 helper causes edcs, find, findmerge, update commands to fail |
#CMBU00045976 |
clearmrgman does not merge elements |
#CMBU00046180 |
xclearcase closes abruptly on report of checkouts |
#CMBU00046225 |
add to source control not recursive |
Table 2 lists the status of problems reported in previous releases.