This file contains descriptions of noteworthy problems in ClearCase Release 4.2.
NOTE: The ClearCase Product Family development group switched to a new change request system since ClearCase 4.0 was released. ID numbers differ between these two systems. This document lists both numbers. The new number appears first and includes a CMBU prefix. The former five-digit number, if one exists, appears in parentheses.
The following are the known problems in ClearCase Release 4.2.
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 (\).
If you use multiple groups to control access, and you use parallel builds, a remote abe does not inherit the group ID from clearmake.
clearmake uses rsh to start an abe process on the remote machine. The user name is not passed by clearmake; it is set by the rsh command. There is no way to pass the effective group. Instead, the abe picks up the user's primary group. For these reasons, starting clearmake in a newgrp shell does not pass the group across the remote abe interface.
Workaround: Create two Bourne-shell scripts
What this script does: The environment variable CLEARCASE_ABE_PN is set to point to this script. The distributed build runs this script instead of /bin/abe.
The script first finds the group setting on the directory in which the build is made, and then copies another script abe.run to the local /tmp, changes the group setting on it and sets the s bit. When this is done, the abe.startup script fires the abe.run script.
What this script does: This script, after being copied and modified by abe.startup, runs the real /bin/abe but with the correct group set.
#!/bin/sh
# Get Vobpathname to the directory where the build will be made
VOB_PATH=$3
# Get View tag
VIEW=$9
# Find out which ls to use
for LS_TEST in /usr/5bin/ls /usr/bin/ls /bin/ls; do
if [ -x $LS_TEST ] ; then
LS=$LS_TEST
fi
done
# Get the group name of the build directory
VIEW_EXT_PATH=/view/${VIEW}$VOB_PATH
CLEARCASE_GROUP=`$LS -lagd $VIEW_EXT_PATH | awk '{print $3}'`
export CLEARCASE_GROUP
# Set the path for clearmake
PATH=${PATH}:${ATRIAHOME:-/usr/atria}/bin
export PATH
# Copy the 'abe.run' script to local /tmp directory, and change group
# to the same as the build directory. Then set the 's' bit on the 'abe.run'
\cp `echo $0 | sed 's@abe\.startup$@abe\.run@'` /tmp/abe.run.$$
chgrp $CLEARCASE_GROUP /tmp/abe.run.$$
chmod g+s /tmp/abe.run.$$
# Run the setuid script
/tmp/abe.run.$$ $*
STAT=$?
# Remove the script
\rm -f /tmp/abe.run.$$
# Exit with same status as the real abe
exit $STAT
#!/bin/sh -p
# Optional debug line
#echo "`uname -n` : `date` : `echo $* | awk '{print $3, $18}'` : $$" >>
/tmp/abe_run.log
exec /bin/abe $*
exit $?
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:
cleartool protect -chmod +w dir-name
where dir-name is the name of the target directory. This command makes the target directory writable before attempting to copy files into it.
On computers 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.
If you have existing Visual C++ projects in ClearCase and want to set the MVFS to be case-preserving or if you want to use snapshot views on those projects, 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 or in a case-preserving MVFS environment require no such renaming to work properly.
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.
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 prompt you to do a graphical merge. It also does not prompt you to look for other items to merge. Instead, elements must be selected and merged manually.
If you change the setting of CCFS in the Options tab of the ClearCase Control Panel program, you must shut down and restart ClearCase before the change takes effect. (You can shut down and start up ClearCase using the Services Startup tab in the ClearCase Control Panel.)
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 quit 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.
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.
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.
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.
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.
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
If you use the Update window (invoked by clearviewupdate) 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 clearviewupdate.
Workaround: Use the command line interface tool xlsvtree to display the version tree.
On Linux and Solaris Intel 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.
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.
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.
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
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. This defect has also been reported as CMBU00030700.
The relocate -update command fails to relocate an element if the element is mastered by a replica at a remote site.
Workaround: To relocate an element that is mastered at another site, you must change the mastership of the element using the chmaster command.
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.
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.
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.
When adjusting MVFS caches as described in Administering ClearCase, 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.
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.
A problem in earlier versions of Windows causes the Date/Time control used in the Settings page of the Job Properties sheet to sometimes switch inappropriately from P.M. to A.M. The Job Properties sheet is part of the Job Scheduler available through the ClearCase Administration Console.
If the current time is P.M. and the user types a new time, instead of using the arrow keys on the keyboard or the spin control on the Date/Time control, the AM/PM box switches to A.M.
This problem appears to be fixed in the latest version of Internet Explorer 5.0.
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 set View >Toolbar, until after you use View >Status 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 the same 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.
If you have a dual-boot computer with Microsoft Word installed on both operating systems and ClearCase installed on only one, you may encounter problems if both of the following things are true:
In this case, Microsoft Word will get a VBA error message at startup time on the system that does not have ClearCase installed.
Workaround: Move the startup folder for one of the operating systems, quit Microsoft Word, and run the ClearCase Microsoft Word Integration Configuration tool. If you have any other templates in the old startup folder, move them also.
There is a known error that occurs when you cancel an Uncheckout confirmation dialog box. It causes Adobe FrameMaker to hang.
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.
clearmake -C Gnu does not interpret escaped percent characters (%) correctly in the $(patsubst) macro.
For example, if you use the statement
PATSUBST := $(patsubst %,\%%,$(WORDS))
in GNU-compatible clearmake, the following incorrect results appear:
$ clearmake -C gnu
echo \a% \b% \c%
\a% \b% \c%
You can use the following workaround in simple cases:
PATSUBST := $(foreachword,$(WORDS),$(subst $(word),%$(word),$(word)))
The first page of the Find Wizard in the Merge Manager displays the Next button improperly. If you select Merge to a snapshot view, the Next button appears even if no snapshot view is selected. Clicking Next causes an error message, fill error, to appear on STDERR and the wizard does not function properly. You must click Cancel and restart the Find Wizard again.
To avoid this error, choose a snapshot view (if Merge to a snapshot view is selected) before clicking Next.
When you invoke a ClearCase graphical interface on a Compaq Alpha platform, you may see this type of warning:
Cannot convert string -*-Menu-Medium-R-Normal--*-120-*-*-P-*-ISO8859-1 to type FontStruct
You can ignore this message because it does not interfere with the functions in ClearCase's graphical interfaces.
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.
This defect was also reported as #CMBU00034225.
If you try to execute a file built in n32 binary format from within the MVFS, the executable or the system may crash. The crash results from a defect in revision level 1.0 of the SGI R5000 chip. This defect has been fixed in revision level 2.1.
Workaround: Upgrade your R5000 chip to revision level 2.1. To check the revision level of your current chip, run the IRIX hinv command.
For the ClearCase-ClearQuest integration to work, you need the printenv command in your path or else the following error message appears: printenv not found. On Solaris Sparc, Solaris Intel, and Reliant UNIX, printenv is located in /usr/ucb; on other systems, it is usually found in /usr/bin.
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"
When running clearexport_cvs, the -A option has no effect if -r has not been specified also.
The output of most cleartool commands that display date information uses an invariant format that ignores regional standards.
The ClearCase Details tool, although it is still available in this release, was replaced by ClearCase Explorer in Release 4.1. ClearCase Details will be removed in a future release.
ClearCase Release 4.x works with Windows NT V4.0, Service Pack 6a, but not with Windows NT V4.0, Service Pack 6.
To determine whether a computer is running Service Pack 6a, follow these steps:
If your computer is running Service Pack 6a, the following line appears in the About box:
Revised Service Pack 6a
rgy_backup does not copy a new rgy_hosts.conf file to any client running the command. To configure a new registry backup server, the rgy_hosts.conf file on the new backup host must be edited to add the backup host name. Any subsequent runs of rgy_backup on that host cause a registry backup to occur.
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.
The checkin comment is taken from the comment text box. If the comment text box is blank, the new version is checked in with the comment string "" (empty string).
On Windows NT, mounting VOBs with the read-only option has no effect.
On some UNIX platforms, mounting VOBs with -options ro works properly; that is, it prevents writes to view-private files within the VOB, but does not prevent other clients from modifying the VOB or any changes that do not use the MVFS, such as some cleartool operations. However, on other UNIX platforms (namely, HP-UX 11.0 and UnixWare), mounting VOBs with -options ro 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.
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.
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 occurs 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 it.
Workaround: Close the file in Word, or use the ClearCase integration with Word.
The Merge Tool 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 the font size or resizing the dialog box does not fix the problem.
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.
ClearCase view servers make anonymous accesses made by users logged in as root on remote hosts. 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 multiple versions of Perl are 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.
The UCM shortcut pane always appears in the ClearCase Explorer. You cannot set the ClearCase 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 quit and restart the ClearCase Explorer, the UCM shortcut pane appears again.
Patch information for ClearCase releases may 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.
ClearQuest (Version 20001A.04.00) provides a security feature that allows you to prevent specific users from seeing specific ClearQuest records. If you use this feature with the UCM-ClearQuest integration, you need to be aware of one restriction and two confusing error messages that you may encounter. To use this feature, you set up user groups and then enable a field in the ClearQuest record type to be the security context field. Do not use the UCM_Project field as the security context field. Doing so could result in assigned activities not appearing in users' MyToDoList queries.
Users who belong to a user group that is not allowed to see the record get the following error message when they attempt to view the record's activity property sheet from a ClearCase GUI:
Unable to display properties of "activity:defect1@\pvob_tag"
#IDispatch error 14094 defect1 doesn't exist or has already been deleted.
Users who belong to a user group that is not allowed to see the record see the following error message 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.
clearmake builds where -J is set to 2 or greater may fail with one of the following errors:
Don't know how to make Interference from another process
This error occurs when clearmake builds target1, which is a dependency of target2, and then evaluates target3, which depends on target2.
For example:
all: target2 target3 target2: target1 target3: target2
This problem has also been reported as #CMBU00050887.
Workaround: Lower the parallelism to -J 1 or disable parallel building.
Anomalous behavior can result when more than one user uses same the snapshot view from the same user account. This usage pattern is neither recommended nor supported for snapshot views, and the results are not guaranteed.
When using the C++ compilation system 3.1, some example programs will fail at link time with an error message similar to the following:
attempt to load old C++ object /usr/atria/shlib/libatriasum.so.
Problem: If you mount a non-clearcase related filesystem, such as cdrom, ext2, etc., from within a view, that now- mounted file system is not visible from outside that view. For example, if you mount the cdrom while inside a view the cdrom contents are visible from only that view.
This occurs on Red Hat 6.2 Linux and Red Hat 7.0 Linux systems.
Explanation: The observed behavior is a result of a difference between Linux and Unix. Linux does all of its lookups through a cache of directory names. Inodes are accessed from these directory entries. This means that file accesses are tied to your directory name space. When you are set to a view, you have effectively changed the root of your process to /view/<viewtag>. This then is linked to the real system root. However, even though it isn't visible to you, your namespace still has the /view/<viewtag> prepended to it. Therefore, when you are set to a view and you mount /dev/cdrom onto /cdrom, for example, you have actually mounted the device on /view/<viewtag>/cdrom.
The MVFS maintains a shadow file system under the view namespace that redirects file references, when possible, to the actual underlying file. However, the mount code directly calls into the MVFS only if it is mounting an MVFS filesystem. There is no way of trapping and redirecting the mount request since the mount itself is handled by the cdrom's filesystem. If the cdrom is mounted outside of a view, it is also visible inside the view. However, if the cdrom is mounted from within the view, it is visible only by using the full view-extended pathname to the mount point.
Under some circumstances, a UCM deliver operation run from the GUI may fail on UnixWare 7.1.1 systems. To ensure that this will not occur, please check that the file descriptor limit is set to 128. You can use the limit command from a C shell or an equivalent command to check or set process resource limits.
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 releases that are fixed in this release.
Problem number | Description |
|---|---|
#CMBU00021926 (#24700) | du -sk gives different file size on Red Hat Linux fixed with a patch |
#CMBU00022765 (#25622) | evaluation license not removed unless ClearCase is removed |
#CMBU00026251 (#29438) | merge from window displays incorrect branch list |
#CMBU00026410 (#29616) | #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 |
#CMBU00040434 | xclearcase fails on dual-headed Solaris machines |
#CMBU00040933 (#39782) | AIX 4.3.3 MVFS is not compatible with 4.3.3.10 or later patch levels |
#CMBU00042349 | z_type managers broken for filenames with embedded blanks |
#CMBU00044722 | Using ClearCase Web Interface, problem overriding primary group |
#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 |
#CMBU00048023 | unreserved checkout preference cannot be overridden by checkout GUI |
#CMBU00049152 | Restrictions on node size in the XML Parser removed |
Table 2 lists the status of problems reported in previous releases.
Problem number | Status | Description |
|---|---|---|
#CMBU00012503 (#14102) | Documented in the READ ME FIRST chapter | cannot tell which products have been installed (Link-only installations) |
#CMBU00024456 (#27488) | Windows 95 not supported | Windows 95 power management makes ClearCase commands unavailable |
#CMBU00025591 (#28717) | Moved to Platform-Specific Guide | on some Compaq Tru64 UNIX systems, atria_start produces warning |
#CMBU00026256 (#29443) | Moved to Platform-Specific Guide | on Compaq Tru64 UNIX systems, error displayed if VOB-tag definitions include symbolic links |
#CMBU00026361 (#29563) | Moved to Platform-Specific Guide | resize of Merge Manager xterms can cause bad data |
#CMBU00026560 (#29789) | Fixed in 3.2.1 | Notes on Merge Manager Display Elements |
#CMBU00028020 (#31405) | Unreproducible | MVFS, VirusScan, and disk access results in process hang |
#CMBU00028325 (#31747) | No plan to fix | cleartool mkbl -preview option is not functional |
#CMBU00031136 (#34872) | Moved to READ ME FIRST chapter | deinstalling ClearCase may remove Web interface views |
#CMBU00032126 (#35972) | No plan to fix | modifying properties of deleted view crashes console |
#CMBU00032785 (#36712) | Fixed in 4.0 | Problems With ClearCase Administration Console if IE4 Not Present |
CMBU00035155 | Not reproducible | Error5 Message when using PowerBuilder integration |
#CMBU00038442 (#37817) | Fixed as #CMBU00030727 | findmerge and Find Wizard cannot traverse symbolic links in snapshot views |
#CMBU00040706 (#39402) | Moved to ClearCase Platform-Specific Guide | on IRIX 6.5.6 and later, CXFS file system is not supported |
#CMBU00040782 (#39625) | Fixed in 4.2 | on Red Hat Linux, Describe command displays error message when multiple files are selected |
#CMBU00040895 (#39741) | Fixed in 4.1 | Dynamic Views Tutorial, Unit 3, does not recognize lowercase string |
#CMBU00040906 (#39754) | Unreproducible | from SGI 6.5.5 system hosting release area, remote install of ClearCase fails |
#CMBU00040933 (#39782) | Fixed as #CMBU00039662 | AIX 4.3.3 MVFS is not compatible with 4.3.3.10 or later patch levels |
#CMBU00040956 (#39806) | No plan to fix | on Reliant UNIX, Solaris Intel, Red Hat Linux, and IRIX platforms, History Browser appears different in snapshot views tutorial |
#CMBU00043577 | Not a bug | using the Version Tree Browser in a snapshot view, problem doing a graphical merge |
#CMBU00045232 | Fixed in 4.1 | Red Hat 6.2 Linux mount command does not properly mount the MVFS |
#CMBU00045368 | Patched in 4.1 | the contributors to the Word merge operation are reversed |
The following problem description was moved to the Restrictions and Guidelines for ClearCase chapter:
The following descriptions of problems were moved to the Restrictions and Guidelines for ClearCase chapter:
| Copyright © 2001 by Rational Software Corporation. All rights reserved. |