Fix list for ClearCase

March 06, 2025

Superseded

March 20, 2024

Initial

March 06, 2025

Superseded

July 15, 2024

Superseded

March 13, 2024

Superseded

October, 2023

Superseded

January 31, 2023

Superseded

December 15, 2022

Initial

March 06, 2025

Superseded

July 15, 2024

Superseded

March 13, 2024

Superseded

October, 2023

Superseded

January 31, 2023

Superseded

July 25, 2022

Superseded

Dec. 22, 2021

Superseded

June 29, 2021

Superseded

Problem:Improper signal handling may cause a hang.

Fix: Signal handling was corrected.

Problem: Adding multiple directories to a web view using rcleartool update -add is failing even though view information is same. and fails silently.

Fix: Modified the view info comparison check against reference to contents of object using equals method.

Problem: Installing or upgrading to ClearCase 9.0.1.7 and later incorrectly installs the ClearCase integration into unsupported versions of Visual Studio. The integration then interferes with the correct operation of the unsupported version of Visual Studio.

Fix:The installation of ClearCase has been updated to list the supported versions of Visual Studio as optional features that the user can enable as desired during the installation. The installation of the integration into the unsupported versions of Visual Studio has been removed.

Problem: Creating Automatic view fails when user region maps are in use and the creating user is not mapped to the WAN server's actual region.

Fix: ClearCase automatic view creation with a region map file has been fixed.

Problem: Memory allocation issue may be noticed, in rare cases, when events are received during shutdown.

Fix: Event received during the shutdown process are handled to address these issues.

Problem: When using the Gnu make compatability mode and specifying a clearmake variable on the command line that contains a reference to another variable, the variable declaration passed down to child makes was incorrect and will cause a clearmake parsing syntax error.

Fix: The variable string being passed to the child clearmake process has been formatted correctly so that the clearmake parsing is correctly done and the build continues.

Problem: ClearTeam Explorer may produce a MalformedResponseException pop-up error when large attributes are encountered.

Fix: ClearTeam Explorer was modified to properly display elements that have large attributes.

Problem: Customer may experience some delays in operations when listing files in automatic view.

Fix: Multi Version File System (MVFS) was modified to avoid creating additional cache files.

Problem:On Linux systems with ext4 filesystems, when accessing directories in that filesystem through a ClearCase view-extended path the ls command may return incomplete results.

Fix: This problem with view-extended access to ext4 directories is fixed in ClearCase 9.0.1.12, 9.0.2.4, and 9.1.0.1.

Problem: Autmounted CC VOBs, when manually umounted are not automatically remounted on the next access if said access is through view extended paths.

Fix: This problem is fixed in ClearCase 9.0.1.12, 9.0.2.4, and 9.1.0.1.

Problem: Loading of activities from PVOB --> Project --> Stream --> Activities was taking more time than it used to take in 9.0.1.4 and before.

Fix:ClearTeam Explorer has been modified to efficiently load activities.

Problem: lad_server.exe(152696): The ClearQuest-UCM OSLC and CMI integrations may core on linux_x86 if a parsed ClearQuest record headline contains characters that cannot be converted to the local code page.

Fix: These integrations should no longer core if a parsed ClearQuest record headline contains characters that cannot be converted to the local code page.

Problem: Customer is unable to see 'CheckedOut but removed' elements from ClearTeam Explorer.

Fix: We have introduced new 'State' column in 'ClearCase Checkouts' view to show the state as 'Checked Out but Removed' for all the files which are deleted from the filesystem. (ClearCase Checkouts' view can be accessed from Window--> Show View --> Other... --> ClearTeam Explorer --> ClearCase Checkouts from ClearTeam Explorer).

Problem: CM Server is-eclipsing property was not recognizing checkouts as eclipsable objects.

Fix: Is-eclipsing calculations are now performed for checkouts.

Problem: ClearCase Search was disabled for dynamic views and (if enabled) was resulting '0 matches', even if matching resources were available.

Fix: ClearCase Search is now enabled for dynamic views and resulting correct match, displaying all the matching resources in 'ClearCase Search'.

Problem: The IBM Rational ClearCase / Cadence Virtuoso integration allows a user to perform SCM operations in both the "Library Manager" and in the editor itself. If a user imports a checkedout cell view into the library manager to checkin a schematic that is currently being edited, changes in the schematic editor can be lost.

Fix: Added a logic for handling the unmanaged lock files.

Problem: In the ClearCase Cadence Integration: If a cell view under virtuoso is checked out with "-unreserved" option, the "Show file status"may throw Errors and not show the status of the cell.

Fix: Checked out with "-unreserved" option has been fixed.

Problem: Running ClearCase with Crowdstrike installed may cause some performance degradation.

Fix: Multi Version File System (MVFS) was modified to handle Crowdstrike demand.

Problem: When reformatvob or db_dumper is invoked and if the root component of the VOB is not available, CRDE validation fails and triggers db__err_abort_call().

Fix: CRDE now validates the failure and continues with db_dumper or reformatvob execution without fail.

Problem: Dev stream creation from a baseline errors out which is expected. However, the displayed error message is not much informative.

Fix: Rephrased the error string to cover all 4 rebase rules mentioned in https://www.ibm.com/support/knowledgecenter/SSSH27_9.0.1/com.ibm.rational.clearcase.cc_ref.doc/ topics/ct_rebase.htm and eliminated the misleading phrase "from the same project".

Problem: Maximum packet size for a VOB replica packet, in config file, was set to much higher value than which is allowed. Due to which, packet shipping was failing for the larger packets which was adhering the maximum size set in config file.

Fix: Changed the maximum packet size to correct one.

Problem: Delivering an already delivered baseline should provide a more informative message.

Fix: When the same baseline is delivered again, following warning message is displayed:- cleartool: Warning: No activities to deliver from stream "d1" to target stream "i1".

Problem: MULTITOOL CHREPLICA ON WINDOWS GUI INCORRECTLY ALLOWS CHANGING THE PRESERVATION MODE FOR A REMOTE VOB REPLICA TO PRESERVING.

Fix: Preservation mode of replica can be change to preserve only if none of the replica from vob-family has preservation mode.

Problem: Rebasing an integration stream to a baseline in the same project fails without providing proper error message.

Fix: Handling the present use case to display error message why rebase is not possible. "Can't rebase to baseline \"%s\"\nof component \"%s\". You can only rebase an integration stream to\nbaselines from other integration streams, or to import or initial baselines.\n".

Problem: Recommended and/or member of composite baseline can be removed by executing "cleartool rmbl" if the baseline is from private VOB only but public VOB baselines removal is not allowed.

Fix: Now both public & private VOB baselines can't be removed, by default and retained consistency. Also introduced a new CLI flag "public", which prevents public VOB removal - same as present behavior.

Problem: The ClearCase UCM deliver dialog cannot be completed after skipping a merge conflict.

Fix: On Restart user will get the dialog to resolve the "merge conflict" not error dialog.

Problem: Microsoft VC 6, 7, and 7.1 Redistributables should no longer be distributed with CC/CQ as they present potential vulnerabilities.

Fix: Microsoft VC 6, 7, and 7.1 Redistributables have been removed from the installation for CC/CQ 9.1. This will not be fixed in 9.0.x. Please upgrade to the 64-bit 9.1.x release to get this fix.

Problem: The graphical help pages on Unix are out of date. They are from version 8.0.

Fix: The graphical help pages on Unix have been updated to match the version of the product.

Problem: The installation of ClearCase 9.1 may cause Installation Manager 1.9.1.4 to crash.

Fix: ClearCase 9.1.0.1 install now succeeds with Installation Manager 1.9.1.4

Problem: The "cleartool find" command, without options shows visible and nvisible (not visible) elements and not only visible elements as documented.

Fix: The "find" topic/man page has been updated in ClearCase 9.1.0.1.

Problem: time_t structure memory size increased on 64-bit platform. This made reformatvob and other DB related functionalities to read value from more memory locations which was not matching the actual value.

Fix: Cleartool Time values are adjusted which fixes present and related memory read issues.

Problem: Multiple display issues with windows native UCM GUIs after install of, or upgrade to, ClearCase 9.1.0.0.

Fix: The ClearCase gui issues have been resolved.

Problem: ClearCase snapshot view move procedure incorrectly states purpose of xcopy /k option.

Fix: The help topic has been updated in ClearCase 9.1.0.1.

Problem: Sporadic kernel crash when closing files under certain conditions.

Fix: MVFS was modified to validate some kernel structures when a file is closing.

Problem: While creating a view with NFS mount point - specifically with extended host path name, host path name was not captured correctly. Hence, the view creation used to fail with incomplete host path name.

Fix: Updated the parsing logic function to populate the host path name completely with which now the view creation succeeds.

Problem: Cleartool commands prompting for comments will not respond to ctrl-c, sigpipes, etc., until after comment is completely supplied.

Fix: Cleartool signal handling was corrected.

Problem: When using the legacy Clearcase gui to run a describe on a ClearCase element on Solaris 11.x the window is not bought up and the command fails silently.

Fix: The script used to implement the legacy Clearcase gui describe command was fixed.

Problem: Using ClearCase clearmake and printing "time spent building with abes: ..." caused clearmake to crash and the build to abort.

Fix: Memory is now freed after printing.

Problem: MVFS wasn't handling the correct error code when trying to read information from registry and the data was bigger than expected, leading MVFS to fail its load process.

Fix: The MVFS is now able to manage itself to deal with bigger data.

Problem: During findmerge, file elements are checked repeatedly in directory passes as well, considering it as a directory, because initially all VOB elements are marked as "not a file". Hence, an error message is printed repeatedly due to the repetitive attempt of searching the file.

Fix: Marked the file element at the initial stage with which now file elements are checked only once in file pass.

October 13, 2020

Initial

Problem: While creating a view with NFS mount point - specifically with extended host path name, host path name was not captured correctly. Hence, the view creation used to fail with incomplete host path name.

Fix: Updated the parsing logic function to populate the host path name completely with which now the view creation succeeds.

Problem:Cleartool commands prompting for comments will not respond to ctrl-c, sigpipes, etc., until after comment is completely supplied.

Fix: Cleartool commands prompting for comments will not respond to ctrl-c, sigpipes, etc., until after comment is completely supplied. So to handle the signals as they arrive, we have used PFM_SELECT_INHIBITED() in imsg_get_input(). Also used "fcntl()" system call to get the current flag states for retaining and set non-blocking state for file descripter before calling fgets(). This helps to unblock the signals in fgets and process by using external pfm_raise() call..

Problem: When using the legacy Clearcase gui to run a describe on a ClearCase element on Solaris 11.x the window is not bought up and the command fails silently.

Fix: The script used to implement the legacy Clearcase gui describe command was fixed.

Problem: Using ClearCase clearmake and printing "time spent building with abes: ..." caused clearmake to crash and the build to abort.

Fix:Memory is now freed after printing.

Problem:MVFS wasn't handling the correct error code when trying to read information from registry and the data was bigger than expected, leading MVFS to fail its load process.

Fix:The correct code error is tested and MVFS is now able to manage itself to deal with bigger data.

Problem: While describing a hyperlink in ClearCase with "-fmt" flag no output is displayed as the events were already scrubbed.

Fix: Added a new warning to notify the user that the hyperlink events were scrubbed.

Problem:During findmerge, file elements are checked repeatedly in directory passes as well, considering it as a directory, because initially all VOB elements are marked as "not a file". Hence, error message is printed repeatedly due to the repetitive attempt of searching the file.

Fix: Marked the file element at the initial stage with which now file elements are checked only once in file pass.

October, 2023

New

January 31, 2023

Superseded

July 25, 2022

Superseded

Dec. 22, 2021

Superseded

June 29, 2021

Superseded

Problem:Improper signal handling may cause a hang.

Fix: Signal handling was corrected.

Problem: Adding multiple directories to a web view using rcleartool update -add is failing even though view information is same. and fails silently.

Fix: Modified the view info comparison check against reference to contents of object using equals method.

Problem: Installing or upgrading to ClearCase 9.0.1.7 and later incorrectly installs the ClearCase integration into unsupported versions of Visual Studio. The integration then interferes with the correct operation of the unsupported version of Visual Studio.

Fix: The installation of ClearCase has been updated to list the supported versions of Visual Studio as optional features that the user can enable as desired during the installation. The installation of the integration into the unsupported versions of Visual Studio has been removed.

Problem: Installing or upgrading to ClearCase 9.0.1.7 and later incorrectly installs the ClearCase integration into unsupported versions of Visual Studio. The integration then interferes with the correct operation of the unsupported version of Visual Studio.

Fix:The installation of ClearCase has been updated to list the supported versions of Visual Studio as optional features that the user can enable as desired during the installation. The installation of the integration into the unsupported versions of Visual Studio has been removed.

Problem: Memory allocation issue may be noticed, in rare cases, when events are received during shutdown.

Fix: Event received during the shutdown process are handled to address these issues.

Problem: When using the Gnu make compatability mode and specifying a clearmake variable on the command line that contains a reference to another variable, the variable declaration passed down to child makes was incorrect and will cause a clearmake parsing syntax error.

Fix: The variable string being passed to the child clearmake process has been formatted correctly so that the clearmake parsing is correctly done and the build continues.

Problem: ClearTeam Explorer may produce a MalformedResponseException pop-up error when large attributes are encountered.

Fix: ClearTeam Explorer was modified to properly display elements that have large attributes.

Problem: Customer may experience some delays in operations when listing files in automatic view.

Fix: Multi Version File System (MVFS) was modified to avoid creating additional cache files.

Problem:On Linux systems with ext4 filesystems, when accessing directories in that filesystem through a ClearCase view-extended path the ls command may return incomplete results.

Fix: This problem with view-extended access to ext4 directories is fixed in ClearCase 9.0.1.12, 9.0.2.4, and 9.1.0.1.

Problem: Autmounted CC VOBs, when manually umounted are not automatically remounted on the next access if said access is through view extended paths.

Fix: This problem is fixed in ClearCase 9.0.1.12, 9.0.2.4, and 9.1.0.1.

Problem: Loading of activities from PVOB --> Project --> Stream --> Activities was taking more time than it used to take in 9.0.1.4 and before.

Fix:ClearTeam Explorer has been modified to efficiently load activities.

Problem: lad_server.exe(152696): The ClearQuest-UCM OSLC and CMI integrations may core on linux_x86 if a parsed ClearQuest record headline contains characters that cannot be converted to the local code page.

Fix: These integrations should no longer core if a parsed ClearQuest record headline contains characters that cannot be converted to the local code page.

Problem: Customer is unable to see 'CheckedOut but removed' elements from ClearTeam Explorer.

Fix: We have introduced new 'State' column in 'ClearCase Checkouts' view to show the state as 'Checked Out but Removed' for all the files which are deleted from the filesystem. (ClearCase Checkouts' view can be accessed from Window--> Show View --> Other... --> ClearTeam Explorer --> ClearCase Checkouts from ClearTeam Explorer).

Problem: CM Server is-eclipsing property was not recognizing checkouts as eclipsable objects.

Fix: Is-eclipsing calculations are now performed for checkouts.

Problem: When working in a dynamic view on Red Hat 7, a problem allocating buffer space for kernel RPC data can cause delays of seconds to hours to occur during some ClearCase operations.

Fix: This problem is fixed in ClearCase 9.0.1.12, 9.0.2.4, and 9.1.0.1.

Problem: ClearCase Search was disabled for dynamic views and (if enabled) was resulting '0 matches', even if matching resources were available.

Fix: ClearCase Search is now enabled for dynamic views and resulting correct match, displaying all the matching resources in 'ClearCase Search'.

Problem: The IBM Rational ClearCase / Cadence Virtuoso integration allows a user to perform SCM operations in both the "Library Manager" and in the editor itself. If a user imports a checkedout cell view into the library manager to checkin a schematic that is currently being edited, changes in the schematic editor can be lost.

Fix: Added a logic for handling the unmanaged lock files.

Problem: In the ClearCase Cadence Integration: If a cell view under virtuoso is checked out with "-unreserved" option, the "Show file status"may throw Errors and not show the status of the cell.

Fix: Checked out with "-unreserved" option has been fixed.

Problem: Running ClearCase with Crowdstrike installed may cause some performance degradation.

Fix: Multi Version File System (MVFS) was modified to handle Crowdstrike demand.

Problem: When reformatvob or db_dumper is invoked and if the root component of the VOB is not available, CRDE validation fails and triggers db__err_abort_call().

Fix: CRDE now validates the failure and continues with db_dumper or reformatvob execution without fail.

Problem: Dev stream creation from a baseline errors out which is expected. However, the displayed error message is not much informative.

Fix: Rephrased the error string to cover all 4 rebase rules mentioned in https://www.ibm.com/support/knowledgecenter/SSSH27_9.0.1/com.ibm.rational.clearcase.cc_ref.doc/   topics/ct_rebase.htm and eliminated the misleading phrase "from the same project".

Problem: Maximum packet size for a VOB replica packet, in config file, was set to much higher value than which is allowed. Due to which, packet shipping was failing for the larger packets which was adhering the maximum size set in config file.

Fix: Changed the maximum packet size to correct one.

Problem: Delivering an already delivered baseline should provide a more informative message.

Fix: When the same baseline is delivered again, following warning message is displayed:- cleartool: Warning: No activities to deliver from stream "d1" to target stream "i1".

Problem: MULTITOOL CHREPLICA ON WINDOWS GUI INCORRECTLY ALLOWS CHANGING THE PRESERVATION MODE FOR A REMOTE VOB REPLICA TO PRESERVING.

Fix: Preservation mode of replica can be change to preserve only if none of the replica from vob-family has preservation mode.

Problem: Rebasing an integration stream to a baseline in the same project fails without providing proper error message.

Fix: Handling the present use case to display error message why rebase is not possible. "Can't rebase to baseline \"%s\"\nof component \"%s\". You can only rebase an integration stream to\nbaselines from other integration streams, or to import or initial baselines.\n".

Problem: Recommended and/or member of composite baseline can be removed by executing "cleartool rmbl" if the baseline is from private VOB only but public VOB baselines removal is not allowed.

Fix: Now both public & private VOB baselines can't be removed, by default and retained consistency. Also introduced a new CLI flag "public", which prevents public VOB removal - same as present behavior.

Problem: The ClearCase UCM deliver dialog cannot be completed after skipping a merge conflict.

Fix: On Restart user will get the dialog to resolve the "merge conflict" not error dialog.

December 18, 2020

Superseded

Problem: Sporadic kernel crash when closing files under certain conditions.

Fix: MVFS was modified to validate some kernel structures when a file is closing.

Problem: When running a build using clearmake, a segment fault may occur if clearmake encounters an extremely large macro expansion.

Fix: Clearmake has been updated to address large macro expansions.

Problem: Clearcase does not make it clear which VOB the below error message refers to. db.m:146 DB__WRONG_SERVER "Process not running on registry specified hostname (%s)\n". Also prints redundant error messages in db_server log.

Fix: To be more specific, vob path name is added in the error message and also added check against vob path name to avoid redundant error messages for each db_server instance.

Problem: Excessive output in lad_log with "Error: Operation "sysutl_user_to_sid" failed:"

Fix: Now for an invalid user the error message is printed only one time in the lad_server log.

Problem: When iterating through label (or branch) types in a Perl script, CAL crashes before returning the list of metadata types to the script.

Fix:CAL label & branch processing no longer results in a stack overflow.

Problem: lad_server.exe(152696): Error: Operation "sysutl_user_to_sid" failed: NT after enabling the async license daemon Reported above error when user sid type is one of the group accounts. Also lad_server log can be overly verbose and grows dangerously quickly with this error.

Fix: Group accounts no longer cause the lad_server to fail.

Problem: While creating a view with NFS mount point - specifically with extended host path name, host path name was not captured correctly. Hence, the view creation used to fail with incomplete host path name.

Fix: Updated the parsing logic function to populate the host path name completely with which now the view creation succeeds.

Problem: File was not getting merged from one branch to other as changing config spec was unloading the element. During merge search, merge happens only for loaded elements.

Fix: During Merge Search, refresh loads the element before initiating merge. So, after merge file and contents would be merged to destination branch

Problem: Hovering over version in GUI vtree browser with multi-line command or other large amount of metadata causes tooltip to flicker.

Fix: In current fix we restrict the number of lines user can see on tool-tip. If number of lines crossed the defined one we are showing message with truncated text "...please use element properties to view full text", so that user can know that tool tip doesn't contain full text and he can see the full comment from properties.

Problem: Cleartool commands prompting for comments will not respond to ctrl-c, sigpipes, etc., until after comment is completely supplied.

Fix: During Cleartool signal handling was corrected.

Problem: When using the legacy Clearcase gui to run a describe on a ClearCase element on Solaris 11.x the window is not brought up and the command fails silently.

Fix: The script used to implement the legacy Clearcase gui describe command was fixed.

Problem: Infocenter page on MVFS settings for samba significantly out of date.

Fix: The "Configuring Rational ClearCase to support Samba" topic has been updated in the help that installs with ClearCase 9.1 and in IBM Knowledge Center for ClearCase 9.1.

Problem: Using ClearCase clearmake and printing "time spent building with abes: ..." caused clearmake to crash and the build to abort.

Fix: Memory is now freed after printing.

Problem: In ClearCase 8.0.x version, when a user tries to check in or cancel checkout for views already open though editor, a warning dialog message were displayed saying “The file is currently open for edit…”. But, in ClearCase 9.0.x, this features were not available.

Fix: These features are now available in ClearCase 9.0.x version.

Problem: MVFS wasn't handling the correct error code when trying to read information from registry and the data was bigger than expected, leading MVFS to fail its load process.

Fix: The MVFS is now able to manage itself to deal with bigger data.

Problem:"Show File Status.." dialog crashes if there is a hidden folder.

Fix: The dialog no longer crashes.

Problem: The path to squidtool was not properly quoted.

Fix: The squidtool application now spawns without issue.

Problem: Visual Studio integration checks out source file parent directory during "remove from project, but not the disk".

Fix: Removing file element will not create new version for directory.

Problem: During Manual Merge on parent directory, sub-directories were also getting merged due to issues in implemented refresh functionality.

Fix: Refresh functionality after manual merge operation has been fixed.

Problem: Vob container's location dbid status was handled properly when a 'checkvob -fix' is done to fix a deleted container status. Due to which error occurred during database dumping process of 'reformatvob'.

Fix: Updated the container's status handling logic with which now 'reformatvob' is dumping and loading database successfully.

Problem: During findmerge, file elements are checked repeatedly in directory passes as well, considering it as a directory, because initially all VOB elements are marked as "not a file". Hence, an error message is printed repeatedly due to the repetitive attempt of searching the file.

Fix: Marked the file element at the initial stage with which now file elements are checked only once in file pass.

Problem: Copy and Paste of the share project in CTE renaming the project/file/folder gets NEP .

Fix: Code changes to handle the Null pointer exception during rename on the Copy-Pasted project are taken care of.

Problem: The ClearCase clearprompt utility fails when the number of characters of a string is greater than 2069 characters.

Fix: Allocation of clearprompt's internal buffer was corrected.

Problem: Cleartool rmver command execution validates for interested version before deleting the selected version. However, similar validation was missing while executing rmbranch command.

Fix: Cleartool rmbranch command execution now validates for any existing baseline in the branch and the command execution does not proceed if any baseline version is found on the branch.

June 25, 2020

Superseded

Problem: MULTITOOL SYNCREPLICA -IMPORT" DELETES SOME PACKETS WHERE IT SHOULD REPORT "... NOT APPLICABLE TO ANY LOCAL VOB REPLICAS"

Fix: Corrected logic for syncreplica import.

Problem: During a deliver to any stream where there is a preop trigger that looks for environment variable "CLEARCASE_POP_KIND" in an integration stream.Since CTE/CCBE were not setting this EV value hence triggers were failing.Same issue was found for Rebase operation.

Fix: Now CTE and CCBE are setting EV "CLEARCASE_POP_KIND" value and same we are able to see in trigger script during Deliver and Rebase (CHECKOUT and CHECKIN) Operations. And also it makes sure that Checkout and Checkin happen only during Deliver/Rebase.

Problem: If an application running on Microsoft Windows tries to read a file in a ClearCase dynamic view using non-cached I/O, after it has already been in use for cached I/O, a deadlock may occur while flushing the cache, and that process and any other processes trying to access that file will hang.

Fix: MVFS handling of the FILE_FLAG_NO_BUFFERING option during file open was modified to eliminate a possible deadlock.

Problem: A segmentation fault may occur when running an executable built within a ClearCase dynamic view on a Red Hat Enterprise Linux 7.8 system.

Fix: Running an executable built within a ClearCase dynamic view no longer seg faults.

Problem: When one or more VOB elements are ACL protected cleartool findmerge doesn't report any differences.

Fix:During cleartool findmerge command execution, ACL protected objects cannot be accessed and due to this failure command execution exits silently. Hence user was not notified about failure reason. Now error string - with problematic object name, will be displayed informing user about the inaccessibility.

Problem: When running 'cleartool setcs' in a batch file with loading nonexisting vob in config spec, the 'update' of the view (implicitly started by the 'setcs') results in errors but the 'errorlevel' always returns 0 - executed successfully".

Fix:To separate the two actions of setting config spec and updating the view, we have exposed "-nupdate" flag from "setcs" implementation. With this when running 'cleartool setcs -nupdate' with config spec, it always returns errorlevel as 0. This operation will not invoke updating the view, So it will not return any error.

Problem: While describing a hyperlink in ClearCase with "-fmt" flag no output is displayed as the events were already scrubbed.

Fix: Added a new warning to notify the user that the hyperlink events were scrubbed.

Problem:Typing CTRL-C in the terminal does not terminate the process or close the GUI window, when using tools such as xcleardiff and xclearcase, after starting an IBM Rational ClearCase GUI from the command prompt.

Fix: Users are now able to terminate, and properly send the process to background, for the GUI windows, after starting an IBM Rational ClearCase GUI from the command prompt.

March 27, 2020

Superseded

Problem: ClearCase Clearmake does not adjust the build concurrency, and it is causing an excessive number of abes and not making appropriate use of abes.

Fix: Clearmake has been changed to limit the number of abe processes to be equal to the -J value or the number of build server hosts, which ever is smaller. Previously, clearmake would start abe processes based on the number of build server hosts, regardless off the -J value, and when a build override situation is encountered, not all of the existing abes were terminated, leaving more abe processes around consuming file descriptors. This change introduces better abe management and limits the number of abes.

Problem: When a CCASE_BLD_HOSTS override changes from one set of hosts to another, the "require" host table is removed, and only "IDLE" abes are terminated. This means that abe's starting jobs, abes actively building, and (possibly) ones in "available" state, are NOT shut down abes accumulate over time.

Fix: Clearmake has been changed to limit the number of abe processes to be equal to the -J value or the number of build server hosts, which ever is smaller. Previously, clearmake would start abe processes based on the number of build server hosts, regardless off the -J value, and when a build override situation is encountered, not all of the existing abes were terminated, leaving more abe processes around consuming file descriptors. This change introduces better abe management and limits the number of abes.

Problem: The ClearCase MVFS disable flag (in the "atria_start" script) was not functional.

Fix:Redefinition of the MVFS flag was resetting the setting and thereby not functional. This APAR fixes that issue and now the flag is functional.

Problem: The ClearCase MVFS disable flag (in the "atria_start" script) was not functional.

Fix: Technote http://www.ibm.com/support/docview.wss?uid=swg27023148 was updated.

Problem: ClearCase change management integrations (CMI) could fail on Windows when connecting to a change management server with an SSL certificate that expires in year 2038 or later

Fix: ClearCase CMI has been corrected to handle SSL certificates expiring in year 2038 or later.

Problem: Send and receive buffer size when entered in KB/MB was not read correctly and creating problem while launching the Multistite applet.

Fix: Tokenizing the receive & send buffer values solved the problem..

Problem: After creating a ClearCase snapshot view on Linux using a registered view storage location with a Windows based view server host the view owner is unable to remove the view.

Fix: The rmview function has been fixed.

Problem: Using ClearCase ClearTeam Explorer to show CMI activities may result in NullPointerExceptions in RTC Integrated environment.

Fix: We did a rollback on FILTERING feature which was the root cause for this NULL POINTER EXCEPTION.

Problem: ClearCase mainframe TSO client operations may fail with "No such file or directory".

Fix: The ClearCase mainframe TSO client was modified to use correct syntax.

Problem: When creating a new stream and adding non-modifiable components using ClearCase ClearTeam Explorer, the original baseline(s) seem to get lost.

Fix: ClearTeam Explorer now correctly manages baselines and components.

Problem: Executing the ClearCase clearprojtool binary creates a duplicate key "Atria " in registry.

Fix:ClearCase clearprojtool registry use / management was corrected.

Problem: ClearCase mainframe TSO client operations may fail with "No such file or directory".

Fix:The ClearCase mainframe TSO client was modified to use correct syntax.

Problem: ClearCase MVFS was not correctly forwarding lock key information to the underlying file system, resulting in a lock conflict when writing to the INI file.

Fix: The lock key is now forwarded to the underlying file system and the write completes successfully.

Problem: ClearCase squidtool ShowActivityProperties throws a double-free error on Linux.

Fix: Memory / string management was corrected.

Problem: A Segmentation fault may occur when running an executable built within a ClearCase dynamic view on a Red Hat Enterprise Linux 8 machine.

Fix: Running an executable built within a ClearCase dynamic view no longer seg faults.

Problem: When adding large numbers of files to source control via ClearCase ClearTeam Explorer, some files "disappear" from the expected directories after the operation completes.

Fix: ClearCase ClearTeam Explorer now correctly adds large numbers of files to source control

Problem: When files are added/removed to a web view using the command line or a GUI other than ClearTeam Explorer, the changes may not be reflected in ClearTeam Explorer, particularly if there are any "unusual" issues with the web view (like a checked-out-but-removed file).

Fix: Client-side code which reads a web view directory, now ignores not-found errors for local copies of files that are known to the server and continues reading. This resolves the problem.

Problem: When using ClearCase to build software using Visual Studio 2017 or newer on Microsoft Windows, the build audit may be incorrect. This would cause some build target's configuration records to be incomplete, and also could cause build targets to fail to rebuild even though another component on which the target depends has changed.

Fix:Audit pointer management was corrected.

Problem: When upgrading the version of ClearCase on a Windows system, a reboot is required to complete the upgrade installation. After that reboot, the system may crash shortly after restarting. It may enter a loop of crashing and restarting, in which case it must be booted in safe mode to allow manual manipulation of files in order to work around the problem.

Fix: The crash is caused by incomplete cleanup of a previous version which is being replaced during the upgrade.

Problem: Right clicking on an excluded file in a ClearCase / VS 2017 project throws *8* unhandled exception.

Fix: While debugging we found that we are passing NULL value while accessing the list without checking the NULL. We just check the NULL condition and it works fine.

Problem: After installing ClearCase 9.0.2 on Windows 10 or newer, the installation will succeed, but after reboot MVFS filesystem will not be started. This message is observed in the system event log: The IBM Rational ClearCase Multi-Version FS for NT10.0 x86_64 service failed to start due to the following error: Windows cannot verify the digital signature for this file.

Fix: This was a product packaging error and the MVFS driver in 9.0.2.1 is correctly signed.

Problem: The ClearCase command "cleartool getlog -around", may miss the first event (if you compare it to a different cleatool getlog command output).

Fix: Internal file pointer / record management was corrected.

Problem: ClearCase clearexport_ccase commands may crash when the length of an attribute name+value exceeds an internal buffer size of 4096.

Fix: During cvt_data file generation, when attribute name and value is copied to buffer having size 4096, checked if total number of characters exceeds 4096. If so, a warning is generated and attribute value is truncated so that it fits into the buffer and would not result in buffer overflow/crash.

Problem: Customer may experience a crash when building using code composer IDE.

Fix: ClearCase was changed to avoid -host, -gpath and -hpath to be used on a non-NAS environment. This fix is available in ClearCase versions 8.0.1.16, 9.0.0.06, 9.0.1.02 and beyond.

Problem: The ClearCase "cleartool rmtag" command may fail on a network mapped drive due to insufficient return code validation.

Fix: Return code are now validated correctly and "cleartool rmtag" command executes successfully on network

Problem: If a Windows ClearCase CCRC WAN server is installed to a directory without spaces (i.e., not the default c:\Program Files or c:\Program Files (x86) directory), a ClearCase upgrade, which cause a preserve and restore of the local CCRC WAN server view storage, damages the view storage security information (because the preserve/restore on Windows does not correctly handle the file/dir security information, including ACLs).

Fix: The CCRC WAN server preserve/restore code was changed to use the Windows robocopy command, which correct

Problem: A problem associating a ClearQuest record to a ClearCase UCM activity gives an incorrect error message in a Japanese language environment.

Fix: The error message has been corrected.

Problem: ClearCase Build Concepts document incorrectly states that clearaudit should work in a snapshot view.

Fix: The help topic corrected.

Problem: When a file was being moving to "lost+found" directory, file was getting renamed and new filename was exceeding the filename length limit supported by OS.

Fix: Before moving a file to "lost+found" directory, check if the new filename will exceed max supported filename length limit. If so, then truncate the filename before renaming the file.

Problem: Operation Not permitted" error on Windows XP/2003 when starting a view stored on Netap 8.2 cDOT.

Fix: ClearCase views stored on Netap 8.2 cDOT no longer experience this issue.

Jan. 7, 2020

Superseded

July 25, 2022

New

March 01, 2022

New

Dec. 22, 2021

Superseded

June 29, 2021

Superseded

Problem:Improper signal handling may cause a hang.

Fix: Signal handling was corrected.

Problem: Adding multiple directories to a web view using rcleartool update -add is failing even though view information is same. and fails silently.

Fix: Modified the view info comparison check against reference to contents of object using equals method.

Problem: Installing or upgrading to ClearCase 9.0.1.7 and later incorrectly installs the ClearCase integration into unsupported versions of Visual Studio. The integration then interferes with the correct operation of the unsupported version of Visual Studio.

Fix: The installation of ClearCase has been updated to list the supported versions of Visual Studio as optional features that the user can enable as desired during the installation. The installation of the integration into the unsupported versions of Visual Studio has been removed.

Problem: Installing or upgrading to ClearCase 9.0.1.7 and later incorrectly installs the ClearCase integration into unsupported versions of Visual Studio. The integration then interferes with the correct operation of the unsupported version of Visual Studio.

Fix:The installation of ClearCase has been updated to list the supported versions of Visual Studio as optional features that the user can enable as desired during the installation. The installation of the integration into the unsupported versions of Visual Studio has been removed.

Problem: Memory allocation issue may be noticed, in rare cases, when events are received during shutdown.

Fix: Event received during the shutdown process are handled to address these issues.

Problem: When using the Gnu make compatability mode and specifying a clearmake variable on the command line that contains a reference to another variable, the variable declaration passed down to child makes was incorrect and will cause a clearmake parsing syntax error.

Fix: The variable string being passed to the child clearmake process has been formatted correctly so that the clearmake parsing is correctly done and the build continues.

Problem: ClearTeam Explorer may produce a MalformedResponseException pop-up error when large attributes are encountered.

Fix: ClearTeam Explorer was modified to properly display elements that have large attributes.

Problem: Customer may experience some delays in operations when listing files in automatic view.

Fix: Multi Version File System (MVFS) was modified to avoid creating additional cache files.

Problem:On Linux systems with ext4 filesystems, when accessing directories in that filesystem through a ClearCase view-extended path the ls command may return incomplete results.

Fix: This problem with view-extended access to ext4 directories is fixed in ClearCase 9.0.1.12, 9.0.2.4, and 9.1.0.1.

Problem: Autmounted CC VOBs, when manually umounted are not automatically remounted on the next access if said access is through view extended paths.

Fix: This problem is fixed in ClearCase 9.0.1.12, 9.0.2.4, and 9.1.0.1.

Problem: Loading of activities from PVOB --> Project --> Stream --> Activities was taking more time than it used to take in 9.0.1.4 and before.

Fix:ClearTeam Explorer has been modified to efficiently load activities.

Problem: lad_server.exe(152696): The ClearQuest-UCM OSLC and CMI integrations may core on linux_x86 if a parsed ClearQuest record headline contains characters that cannot be converted to the local code page.

Fix: These integrations should no longer core if a parsed ClearQuest record headline contains characters that cannot be converted to the local code page.

Problem: Customer is unable to see 'CheckedOut but removed' elements from ClearTeam Explorer.

Fix: We have introduced new 'State' column in 'ClearCase Checkouts' view to show the state as 'Checked Out but Removed' for all the files which are deleted from the filesystem. (ClearCase Checkouts' view can be accessed from Window--> Show View --> Other... --> ClearTeam Explorer --> ClearCase Checkouts from ClearTeam Explorer).

Problem: CM Server is-eclipsing property was not recognizing checkouts as eclipsable objects.

Fix: Is-eclipsing calculations are now performed for checkouts.

Problem: When working in a dynamic view on Red Hat 7, a problem allocating buffer space for kernel RPC data can cause delays of seconds to hours to occur during some ClearCase operations.

Fix: This problem is fixed in ClearCase 9.0.1.12, 9.0.2.4, and 9.1.0.1.

Problem: ClearCase Search was disabled for dynamic views and (if enabled) was resulting '0 matches', even if matching resources were available.

Fix: ClearCase Search is now enabled for dynamic views and resulting correct match, displaying all the matching resources in 'ClearCase Search'.

Problem: The IBM Rational ClearCase / Cadence Virtuoso integration allows a user to perform SCM operations in both the "Library Manager" and in the editor itself. If a user imports a checkedout cell view into the library manager to checkin a schematic that is currently being edited, changes in the schematic editor can be lost.

Fix: Added a logic for handling the unmanaged lock files.

Problem: In the ClearCase Cadence Integration: If a cell view under virtuoso is checked out with "-unreserved" option, the "Show file status"may throw Errors and not show the status of the cell.

Fix: Checked out with "-unreserved" option has been fixed.

Problem: Running ClearCase with Crowdstrike installed may cause some performance degradation.

Fix: Multi Version File System (MVFS) was modified to handle Crowdstrike demand.

Problem: When reformatvob or db_dumper is invoked and if the root component of the VOB is not available, CRDE validation fails and triggers db__err_abort_call().

Fix: CRDE now validates the failure and continues with db_dumper or reformatvob execution without fail.

Problem: Dev stream creation from a baseline errors out which is expected. However, the displayed error message is not much informative.

Fix: Rephrased the error string to cover all 4 rebase rules mentioned in https://www.ibm.com/support/knowledgecenter/SSSH27_9.0.1/com.ibm.rational.clearcase.cc_ref.doc/
topics/ct_rebase.htm and eliminated the misleading phrase "from the same project".

Problem: Maximum packet size for a VOB replica packet, in config file, was set to much higher value than which is allowed. Due to which, packet shipping was failing for the larger packets which was adhering the maximum size set in config file.

Fix: Changed the maximum packet size to correct one.

Problem: Delivering an already delivered baseline should provide a more informative message.

Fix: When the same baseline is delivered again, following warning message is displayed:- cleartool: Warning: No activities to deliver from stream "d1" to target stream "i1".

Problem: MULTITOOL CHREPLICA ON WINDOWS GUI INCORRECTLY ALLOWS CHANGING THE PRESERVATION MODE FOR A REMOTE VOB REPLICA TO PRESERVING.

Fix: Preservation mode of replica can be change to preserve only if none of the replica from vob-family has preservation mode.

Problem: Rebasing an integration stream to a baseline in the same project fails without providing proper error message.

Fix: Handling the present use case to display error message why rebase is not possible. "Can't rebase to baseline \"%s\"\nof component \"%s\". You can only rebase an integration stream to\nbaselines from other integration streams, or to import or initial baselines.\n".

Problem: Recommended and/or member of composite baseline can be removed by executing "cleartool rmbl" if the baseline is from private VOB only but public VOB baselines removal is not allowed.

Fix: Now both public & private VOB baselines can't be removed, by default and retained consistency. Also introduced a new CLI flag "public", which prevents public VOB removal - same as present behavior.

Problem: The ClearCase UCM deliver dialog cannot be completed after skipping a merge conflict.

Fix: On Restart user will get the dialog to resolve the "merge conflict" not error dialog.

December 18, 2020

Superseded

Problem: Sporadic kernel crash when closing files under certain conditions.

Fix: MVFS was modified to validate some kernel structures when a file is closing.

Problem: When running a build using clearmake, a segment fault may occur if clearmake encounters an extremely large macro expansion.

Fix: Clearmake has been updated to address large macro expansions.

Problem: Clearcase does not make it clear which VOB the below error message refers to. db.m:146 DB__WRONG_SERVER "Process not running on registry specified hostname (%s)\n". Also prints redundant error messages in db_server log.

Fix: To be more specific, vob path name is added in the error message and also added check against vob path name to avoid redundant error messages for each db_server instance.

Problem: Excessive output in lad_log with "Error: Operation "sysutl_user_to_sid" failed:"

Fix: Now for an invalid user the error message is printed only one time in the lad_server log.

Problem: When iterating through label (or branch) types in a Perl script, CAL crashes before returning the list of metadata types to the script.

Fix:CAL label & branch processing no longer results in a stack overflow.

Problem: lad_server.exe(152696): Error: Operation "sysutl_user_to_sid" failed: NT after enabling the async license daemon Reported above error when user sid type is one of the group accounts. Also lad_server log can be overly verbose and grows dangerously quickly with this error.

Fix: Group accounts no longer cause the lad_server to fail.

Problem: While creating a view with NFS mount point - specifically with extended host path name, host path name was not captured correctly. Hence, the view creation used to fail with incomplete host path name.

Fix: Updated the parsing logic function to populate the host path name completely with which now the view creation succeeds.

Problem: File was not getting merged from one branch to other as changing config spec was unloading the element. During merge search, merge happens only for loaded elements.

Fix: During Merge Search, refresh loads the element before initiating merge. So, after merge file and contents would be merged to destination branch

Problem: Hovering over version in GUI vtree browser with multi-line command or other large amount of metadata causes tooltip to flicker.

Fix: In current fix we restrict the number of lines user can see on tool-tip. If number of lines crossed the defined one we are showing message with truncated text "...please use element properties to view full text", so that user can know that tool tip doesn't contain full text and he can see the full comment from properties.

Problem: Cleartool commands prompting for comments will not respond to ctrl-c, sigpipes, etc., until after comment is completely supplied.

Fix: During Cleartool signal handling was corrected.

Problem: When using the legacy Clearcase gui to run a describe on a ClearCase element on Solaris 11.x the window is not brought up and the command fails silently.

Fix: The script used to implement the legacy Clearcase gui describe command was fixed.

Problem: Infocenter page on MVFS settings for samba significantly out of date.

Fix: The "Configuring Rational ClearCase to support Samba" topic has been updated in the help that installs with ClearCase 9.1 and in IBM Knowledge Center for ClearCase 9.1.

Problem: Using ClearCase clearmake and printing "time spent building with abes: ..." caused clearmake to crash and the build to abort.

Fix: Memory is now freed after printing.

Problem: In ClearCase 8.0.x version, when a user tries to check in or cancel checkout for views already open though editor, a warning dialog message were displayed saying “The file is currently open for edit…”. But, in ClearCase 9.0.x, this features were not available.

Fix: These features are now available in ClearCase 9.0.x version.

Problem: MVFS wasn't handling the correct error code when trying to read information from registry and the data was bigger than expected, leading MVFS to fail its load process.

Fix: The MVFS is now able to manage itself to deal with bigger data.

Problem:"Show File Status.." dialog crashes if there is a hidden folder.

Fix: The dialog no longer crashes.

Problem: The path to squidtool was not properly quoted.

Fix: The squidtool application now spawns without issue.

Problem: Visual Studio integration checks out source file parent directory during "remove from project, but not the disk".

Fix: Removing file element will not create new version for directory.

Problem: During Manual Merge on parent directory, sub-directories were also getting merged due to issues in implemented refresh functionality.

Fix: Refresh functionality after manual merge operation has been fixed.

Problem: Vob container's location dbid status was handled properly when a 'checkvob -fix' is done to fix a deleted container status. Due to which error occurred during database dumping process of 'reformatvob'.

Fix: Updated the container's status handling logic with which now 'reformatvob' is dumping and loading database successfully.

Problem: During findmerge, file elements are checked repeatedly in directory passes as well, considering it as a directory, because initially all VOB elements are marked as "not a file". Hence, an error message is printed repeatedly due to the repetitive attempt of searching the file.

Fix: Marked the file element at the initial stage with which now file elements are checked only once in file pass.

Problem: Copy and Paste of the share project in CTE renaming the project/file/folder gets NEP .

Fix: Code changes to handle the Null pointer exception during rename on the Copy-Pasted project are taken care of.

Problem: The ClearCase clearprompt utility fails when the number of characters of a string is greater than 2069 characters.

Fix: Allocation of clearprompt's internal buffer was corrected.

Problem: Cleartool rmver command execution validates for interested version before deleting the selected version. However, similar validation was missing while executing rmbranch command.

Fix: Cleartool rmbranch command execution now validates for any existing baseline in the branch and the command execution does not proceed if any baseline version is found on the branch.

June 25 2020

Superseded

Problem: MULTITOOL SYNCREPLICA -IMPORT" DELETES SOME PACKETS WHERE IT SHOULD REPORT "... NOT APPLICABLE TO ANY LOCAL VOB REPLICAS"

Fix: Corrected logic for syncreplica import.

Problem: During a deliver to any stream where there is a preop trigger that looks for environment variable "CLEARCASE_POP_KIND" in an integration stream.Since CTE/CCBE were not setting this EV value hence triggers were failing.Same issue was found for Rebase operation.

Fix: Now CTE and CCBE are setting EV "CLEARCASE_POP_KIND" value and same we are able to see in trigger script during Deliver and Rebase (CHECKOUT and CHECKIN) Operations.And also it makes sure that Checkout and Checkin happen only during Deliver/Rebase.

Problem: When one or more VOB elements are ACL protected cleartool diff doesn't report any differences.

Fix: During cleartool diff command execution, ACL protected objects cannot be accessed and due to this failure command execution exits silently. Hence user was not notified about failure reason. Now error string - with problematic object name, will be displayed informing user about the inaccessibility.

Problem: Label function fails for some libraries.

Fix: The label function was repaired.

Problem:Sometimes cleartool getcache -mvfs command output may not be coherent with scaling values shown in Clearcase Control Panel.

Fix: Clearcase Control Panel was modified to fix that behavior.

Problem: Using clearmake in a distributed environment with ClearCase 9.0.1.09, there might be a very specific scenario where the makefile includes some targets that cannot be build in parallel that are identified using the .NOTPARALLEL directive, and the not parallel targets are also to be directed to a list of specific build servers (e.g. using the CCASE_BLD_HOSTS environment variable). With this scenario, it is possible the resulting build may become stuck and hang and not make any progress if one of the specific build servers has an error starting an abe, or if the abe is very slow in responding.

Fix:If the situation occurs, where a target is specified as not being able to be built in parallel (.NOTPARALLEL directive used) and the target is directed to a specific build server as identified in the makefile using the CCASE_BLD_HOSTS environment variable, and the resulting build server has an issue starting an abe, or the abe is slow to respond, clearmake will now re-schedule that target to be built on a different build server and the build will continue.

Problem: ClearTeam Explorer change_sets not visible in CTE CQ interface.

Fix: While creating the 'ClearQuest Details' view we have made those tools to get listed in toolbar with proper actions

Problem: If an application running on Microsoft Windows tries to read a file in a ClearCase dynamic view using non-cached I/O, after it has already been in use for cached I/O, a deadlock may occur while flushing the cache, and that process and any other processes trying to access that file will hang.

Fix: MVFS handling of the FILE_FLAG_NO_BUFFERING option during file open was modified to eliminate a possible deadlock.

Problem: A segmentation fault may occur when running an executable built within a ClearCase dynamic view on a Red Hat Enterprise Linux 7.8 system.

Fix: Running an executable built within a ClearCase dynamic view no longer seg faults.

Problem: When one or more VOB elements are ACL protected cleartool findmerge doesn't report any differences.

Fix:During cleartool findmerge command execution, ACL protected objects cannot be accessed and due to this failure command execution exits silently. Hence user was not notified about failure reason. Now error string - with problematic object name, will be displayed informing user about the inaccessibility

Problem: When running 'cleartool setcs' in a batch file with loading nonexisting vob in config spec, the 'update' of the view (implicitly started by the 'setcs') results in errors but the 'errorlevel' always returns 0 - executed successfully".

Fix:To separate the two actions of setting config spec and updating the view, we have exposed "-nupdate" flag from "setcs" implementation. With this when running 'cleartool setcs -nupdate' with config spec, it always returns errorlevel as 0. This operation will not invoke updating the view, So it will not return any error.

Problem: While describing a hyperlink in ClearCase with "-fmt" flag no output is displayed as the events were already scrubbed.

Fix: Added a new warning to notify the user that the hyperlink events were scrubbed.

Problem:Typing CTRL-C in the terminal does not terminate the process or close the GUI window, when using tools such as xcleardiff and xclearcase, after starting an IBM Rational ClearCase GUI from the command prompt.

Fix: Users are now able to terminate, and properly send the process to background, for the GUI windows, after starting an IBM Rational ClearCase GUI from the command prompt.

March 27 2020

Superseded

Problem: ClearCase Clearmake does not adjust the build concurrency, and it is causing an excessive number of abes and not making appropriate use of abes.

Fix: Clearmake has been changed to limit the number of abe processes to be equal to the -J value or the number of build server hosts, which ever is smaller. Previously, clearmake would start abe processes based on the number of build server hosts, regardless off the -J value, and when a build override situation is encountered, not all of the existing abes were terminated, leaving more abe processes around consuming file descriptors. This change introduces better abe management and limits the number of abes.

Problem: When a CCASE_BLD_HOSTS override changes from one set of hosts to another, the "require" host table is removed, and only "IDLE" abes are terminated. This means that abe's starting jobs, abes actively building, and (possibly) ones in "available" state, are NOT shut down abes accumulate over time.

Fix: Clearmake has been changed to limit the number of abe processes to be equal to the -J value or the number of build server hosts, which ever is smaller. Previously, clearmake would start abe processes based on the number of build server hosts, regardless off the -J value, and when a build override situation is encountered, not all of the existing abes were terminated, leaving more abe processes around consuming file descriptors. This change introduces better abe management and limits the number of abes.

Problem: The ClearCase MVFS disable flag (in the "atria_start" script) was not functional.

Fix:Redefinition of the MVFS flag was resetting the setting and thereby not functional. This APAR fixes that issue and now the flag is functional.

Problem: The ClearCase MVFS disable flag (in the "atria_start" script) was not functional.

Fix: Technote http://www.ibm.com/support/docview.wss?uid=swg27023148 was updated.

Problem: ClearCase change management integrations (CMI) could fail on Windows when connecting to a change management server with an SSL certificate that expires in year 2038 or later.

Fix: ClearCase CMI has been corrected to handle SSL certificates expiring in year 2038 or later.

Problem: Send and receive buffer size when entered in KB/MB was not read correctly and creating problem while launching the Multistite applet.

Fix: Tokenizing the receive & send buffer values solved the problem..

Problem: After creating a ClearCase snapshot view on Linux using a registered view storage location with a Windows based view server host the view owner is unable to remove the view.

Fix: The rmview function has been fixed.

Problem:regression Using ClearCase ClearTeam Explorer to show CMI activities may result in NullPointerExceptions in RTC Integrated environment.

Fix: We did a rollback on FILTERING feature which was the root cause for this NULL POINTER EXCEPTION.

Problem: ClearCase mainframe TSO client operations may fail with "No such file or directory".

Fix: The ClearCase mainframe TSO client was modified to use correct syntax.

Problem: When creating a new stream and adding non-modifiable components using ClearCase ClearTeam Explorer, the original baseline(s) seem to get lost.

Fix: ClearTeam Explorer now correctly manages baselines and components.

Problem: Executing the ClearCase clearprojtool binary creates a duplicate key "Atria " in registry.

Fix:ClearCase clearprojtool registry use / management was corrected.

Problem: ClearCase mainframe TSO client operations may fail with "No such file or directory".

Fix:The ClearCase mainframe TSO client was modified to use correct syntax.

Problem: ClearCase MVFS was not correctly forwarding lock key information to the underlying file system, resulting in a lock conflict when writing to the INI file.

Fix: The lock key is now forwarded to the underlying file system and the write completes successfully.

Problem: ClearCase squidtool ShowActivityProperties throws a double-free error on Linux.

Fix: Memory / string management was corrected.

Problem: A Segmentation fault may occur when running an executable built within a ClearCase dynamic view on a Red Hat Enterprise Linux 8 machine.

Fix: Running an executable built within a ClearCase dynamic view no longer seg faults.

Problem: When adding large numbers of files to source control via ClearCase ClearTeam Explorer, some files "disappear" from the expected directories after the operation completes.

Fix: ClearCase ClearTeam Explorer now correctly adds large numbers of files to source control

Problem: When files are added/removed to a web view using the command line or a GUI other than ClearTeam Explorer, the changes may not be reflected in ClearTeam Explorer, particularly if there are any "unusual" issues with the web view (like a checked-out-but-removed file).

Fix: Client-side code which reads a web view directory, now ignores not-found errors for local copies of files that are known to the server and continues reading. This resolves the problem.

Problem: When using ClearCase to build software using Visual Studio 2017 or newer on Microsoft Windows, the build audit may be incorrect. This would cause some build target's configuration records to be incomplete, and also could cause build targets to fail to rebuild even though another component on which the target depends has changed.

Fix:Audit pointer management was corrected.

Problem: When upgrading the version of ClearCase on a Windows system, a reboot is required to complete the upgrade installation. After that reboot, the system may crash shortly after restarting. It may enter a loop of crashing and restarting, in which case it must be booted in safe mode to allow manual manipulation of files in order to work around the problem.

Fix: The crash is caused by incomplete cleanup of a previous version which is being replaced during the upgrade.

Problem: Right clicking on an excluded file in a ClearCase / VS 2017 project throws *8* unhandled exception.

Fix: While debugging we found that we are passing NULL value while accessing the list without checking the NULL. We just check the NULL condition and it works fine.

Problem: The ClearCase command "cleartool getlog -around", may miss the first event (if you compare it to a different cleatool getlog command output).

Fix: Internal file pointer / record management was corrected.

Problem: ClearCase clearexport_ccase commands may crash when the length of an attribute name+value exceeds an internal buffer size of 4096.

Fix: During cvt_data file generation, when attribute name and value is copied to buffer having size 4096, checked if total number of characters exceeds 4096. If so, a warning is generated and attribute value is truncated so that it fits into the buffer and would not result in buffer overflow/crash.

Problem: Customer may experience a crash when building using code composer IDE.

Fix: ClearCase was changed to avoid -host, -gpath and -hpath to be used on a non-NAS environment. This fix is available in ClearCase versions 8.0.1.16, 9.0.0.06, 9.0.1.02.

Problem: The ClearCase "cleartool rmtag" command may fail on a network mapped drive due to insufficient return code validation.

Fix: Return code are now validated correctly and "cleartool rmtag" command executes successfully on network mapped drive.

Problem: If a Windows ClearCase CCRC WAN server is installed to a directory without spaces (i.e., not the default c:\Program Files or c:\Program Files (x86) directory), a ClearCase upgrade, which cause a preserve and restore of the local CCRC WAN server view storage, damages the view storage security information (because the preserve/restore on Windows does not correctly handle the file/dir security information, including ACLs).

Fix: The CCRC WAN server preserve/restore code was changed to use the Windows robocopy command, which corrects this issue

Problem: A problem associating a ClearQuest record to a ClearCase UCM activity gives an incorrect error message in a Japanese language environment.

Fix: The error message has been corrected.

Problem: ClearCase Build Concepts document incorrectly states that clearaudit should work in a snapshot view.

Fix: The help topic corrected.

Problem: When a file was being moving to "lost+found" directory, file was getting renamed and new filename was exceeding the filename length limit supported by OS.

Fix: Before moving a file to "lost+found" directory, check if the new filename will exceed max supported filename length limit. If so, then truncate the filename before renaming the file.

Problem: Operation Not permitted" error on Windows XP/2003 when starting a view stored on Netap 8.2 cDOT

Fix: ClearCase views stored on Netap 8.2 cDOT no longer experience this issue.

Sept 27 2019

Superseded

When using ClearTeam Explorer to examine the properties of a version or element, the properties window may not display any data until the "Show Properties" command is selected multiple times. Then it will begin working normally.

Fix:TThe Properties window in ClearTeam Explorer now displays data correctly when "Show Properties" command is selected.

Problem: ClearCase clearmake may print out a warning message with an invalid signal number when a sub-process exits without properly being detected by the abe.

Fix: The invalid signal number is corrected to provide the correct number, and a few more checks are performed to provide more specific information on the process termination.

Problem: ClearCase clearmake may print out a warning message with an invalid signal number when a sub-process exits without properly being detected by the abe.

Fix:The invalid signal number is corrected to provide the correct number, and a few more checks are performed to provide more specific information on the process termination.

Problem: IBM Knowledge Center has out of date statements for ClearCase 9.0.1

Fix:The help topic has been updated.

Problem:An option used during install of the GSKit on Solaris zones was depreciated in Solaris 11. This would cause the GSKit installation to fail and subsequently the ClearCase or ClearQuest install would also fail.

Fix: The GSKit install for Solaris 11 was changed to use a Solaris environment variable to allow the install to complete successfully.

Problem: ClearCase vob_server RPCs may timeout due to windows socket irregularities causing misdirected RPCs.

Fix: ClearCase windows port management code was modified in order to resolve this issue.

Problem: ClearCase weekly log scrubbing completes successfully but blurts Perl syntax warnings.

Fix: The ClearCase weekly log scrubbing script now properly closes the directory before function execution completes.

Problem: ClearCase sites with company-wide groups having thousands of long-named users may cause ClearCase core to run out of buffer space.

Fix: ClearCase core now uses a larger buffer and has the ability to make the buffer larger.

Problem: The ClearCase Cadence Integration ClearCase4Cds label function fails for cells with special character in cell name

Fix: Now we handle special character in the cellname and libname. we are using cadence api e.g. nmpCDBAToLibraryUnix to change name from CDBA to Library namespace and nmpLibraryUnixToCDBA from Library namespace to CDBA.

Problem:When ClearCase Unix jobs run and attempt to send status emails, the notify program may crash if the mail program fails.

Fix: ClearCase Unix notify functionality now properly detects mail program failures.

Problem: The ClearCase CMI JIRA integration reports invalid XML or invalid JSON (version dependent) when attempting to run ct settask -find.

Fix: ClearCase The ClearCase CMI JSON parser now correctly parses the query response returned from the JIRA server.

Problem:Clearcase Windows may crash on high stressed system.

Fix: Clearcase MVFS (Multi Version File System) was changed to avoid a crash protecting shared data.

Problem: The ClearCase albd_server, when running with multiple registry worker threads, sometimes gets into an infinite loop..

Fix: The albd_server, when running with multiple registry worker threads, should no longer get into an infinite loop.

Problem: ClearCase Omake may stop functioning on the second execution of a macro used by multiple targets

Fix: Omake has been updated to properly handle multiple uses of macros.

Problem: Installing ClearCase 9.0.1.7 on Centos you may encounter: Internal error in MVFS panel.

Fix: OS version checking has been corrected in ClearCase install.

Problem: For a VOB with a very large number of label types, exploring label types in ClearTeam Explorer may not fully populate the details (Type/Created/Scope/Lock) for all label types found.

Fix: ClearTeam Explorer property fetching has been fixed.

Problem: The base CC/CQ integration (v2Perl) hangs, after updating to CC 9.0.1.6, due to missing expected environment variables in trigger environment.

Fix: As a solution, we have added both CCASE and ATRIA prefix for env variables for clearcase.

Problem: After upgrading to ClearCase 9.0.1.7, the ClearCase explorer no longer displays the entire context menu in the view root of a dynamic view.

Fix: The context menu for the root of dynamic views in the ClearCase explorer has been corrected to show all expected options.

Problem: The ClearCase Cadence Integration may fail on checkin of a category in ClearCase 9.0.1.6 integrated with Cadence 6.1.7

Fix: This issue was resolved by fetching the correct category name.

Problem: ClearCase Build Concepts document incorrectly states that clearaudit should work in a snapshot view.

Fix: The help topic is corrected.

Problem: ClearCase and ClearQuest installs the Microsoft VC++ 2008 run-time to support the IBM GSKit library. The Microsoft VC++ 2008 run-time has gone out of support and needs to be updated.

Fix:The GSKit has been updated to version 8.0.55.9 which depends on the Microsoft VC++ 2013 run-time instead of the Microsoft VC++ 2008 run-time. With this update ClearCase and ClearQuest will no longer install the Microsoft VC++ 2008 run-time.

Problem: A ClearCase UCM environment variable, called CCASE_DISABLE_FDN_REUSE, was added in ClearCase V8.0. When set to TRUE, this environment variable prevents the creation of duplicate baselines when a foundation baseline has already been reused in a previous "make baseline" operation and when the baseline that has been reused resides in a PVOB which is not under the same AdminVOB hierarchy as the PVOB where the new baseline is being created. Use of the variable requires setting the environment variable on all clients.

Fix: Added a UCM policy to allow for setting the behavior once, on the server; all clients with this patch will use the UCM policy setting.

June 20 2019

Superseded

When ClearCase is starting on a Solaris 11 update 4 system, the following warning message can be seen: /opt/rational/clearcase/sol_x86/kvm/5.11_4/amd64/mvfs: use of symbol '_depends_on[]' is deprecated: "strmod/rpcmod"

Fix:The ClearCase source code which references the deprecated symbol '_depends_on[]' has been updated to replace that reference with options passed to the linker to encode that dependency in the MVFS module at link time. There is no functional change to the MVFS, and the warning message at load time is eliminated.

Problem: ClearCase clearmake may print out a warning message with an invalid signal number when a sub-process exits without properly being detected by the abe.

Fix:The invalid signal number is corrected to provide the correct number, and a few more checks are performed to provide more specific information on the process termination.

Problem: ClearCase umask management was changed due to multi-thread considerations. Long lived CtCmd processes only obtained umask once (at startup).

Fix: CtCmd processes now correctly obtain the process umask.

Problem: The ClearCase cleartool checkvob sub-command may erroneously report mis-protected containers on Windows.

Fix: The fix allows checkvob to properly detect container protections on Windows.

Problem: A ClearCase credmap done on a UNIX host, to a Windows server can map group IDs, but cannot map user IDs.

Fix: ClearCase credmap processing has been corrected.

Problem: ClearCase reop triggers do not block the request for mastership in synchronous request for mastership checkouts and mkelems.

Fix: Preop triggers on reqmaster will now fire during synchronous request for mastership checkouts and mkelems, and will allow the User to block requests for mastership during those operations.

Problem: The newest ClearCase CtCmd bits aren't available on CPAN.

Fix: ClearCase CtCmd bits are available on the Rational Fix Portal.

March 21 2019

Superseded

Under high transaction loads, Windows ClearCase servers are disproportionately impacted by file lock contention on vista.* files. The underlying cause is that the OS file lock API used by the database core has a fixed one-second retry interval. As such, any contended locks will introduce an immediate one-second delay in the operations in question.

Fix:ClearCase Windows and Unix now use NON-blocking lock calls

Problem: When you are working in ClearTeam Explorer on a Portuguese Microsoft Windows Operating System, you may encounter an error after clicking "Compare with predecessor" version.

Fix: Fix the the broken Portuguese translation for Compare/Merge preference.

Problem: In the RTC client where the ClearCase CTE plugin is installed, the user encounters an internal error occurred during: "Getting toolbar activities" when click a UCM view from ClearTeam Navigator.

Fix: Fix the code where the unnecessary exception was thrown.

Problem: ClearCase displays 8.x help on windows.

Fix: ClearCase now displays 9.x help on windows.

Problem: The ClearCase CCRC update site located by http://CCRCWANServerIPAddress/ccrc/update contained out-of-date information, including hyperlinks to the ClearCase 8.0 Information Center, instructions for installing the CTE Eclipse plug-in into versions of Eclipse that are no longer supported.

Fix: Revise the site page with up-to-date information.

Problem:A new ClearCase UCM activity is not selected when created during checkout/add to source control in ctexplorer

Fix: Previously checkout/add to source control dialogs drop down was not registered for refresh when an activity gets created. Now it is fixed.

Problem: Sending Multisite packets from fully-64-bit 9.0.1.5 hosts fails with "no more memory available" errors.

Fix: This problem was caused by using an unititialized u_long in the call getsockopt() rather than an int. getsockopt() returns 4 bytes but the top 4 bytes contain uninitialized junk.

Problem: The ClearCase rccbuild application correctly blocks on a version mismatch between a ClearCase build client and the Mainframe Connectors. The version string were being incorrectly maintained.

Fix: The ClearCase Mainframe Connector version string was corrected.

Problem: A ClearCase rebase -preview can fail to take overrides into account, rendering it unable to return a list of potentially included activities, even though the actual rebase succeeds.

Fix: A ClearCase rebase -preview will properly assess overrides, allowing it to return a list of potentially included activities.

Problem: During a ClearCase rebase a foundation hyperlink may be removed, but if the rebase operation fails for some reason a subsequent rebase then tries to remove the same foundation hyperlink again, but that will fail with a missing hyperlink error.

Fix:Please contact HCL ClearCase support for instructions to enable information collection

Problem:You may find that the steps after IKJEFT01, IKJEFT1A and IKJEFT1Bb don't work in JCL scripts. The build may fail with "the system or user abend S047 R=NULL was issued."

Fix: ClearCase Mainframe Connector APF mode was corrected.

Problem: ClearCase trigger context isn't always clear. The mkelem command from the integration has no parent-op for check-in that happens during that.

Fix: Checkin and check-out happening during mkelem command will have "mkelem" as parent operation

Problem: When working in an Rational ClearCase integration with Microsoft Visual Studio 2015, you may find an unexpected mkbranch operation occurs if your config spec contains an automatic mkbranch rule and you open files that are not in your project.

Fix: CAL was fixed to properly report "owner" and "group" values without corrupting memory.

Problem: rcleartool lsproject was requiring a "project:" selector prefix when it should not have been needed.

Fix: Root cause was due to a new undocumented feature (IntelliSense support) added by Microsoft in VS. Now it is handled properly.

Problem: DOCUMENTATION SHOULD INCLUDE THAT A DATABASE SCHEMA 12 CC VIEW CANNOT BE USED ON 8.0.1.X

Fix: Added "New view database schema" section to the "what's new" document for ClearCase 9.0. https://www.ibm.com/support/docview.wss?uid=swg21972269

Problem: "RCLEARTOOL -VER" DOESN'T GIVE CORRECT VERSION

Fix: rcleartool returns correct version information.

Nov 15 2018

Superseded

Problem: On Windows Server 2008R2 the installer was incorrectly warning the user that the operating system was not supported. Support for Windows Server 2008R2 was removed in version 9.0.1 but reinstated in 9.0.1.3.

Fix: Since Windows Server 2008R2 is again a supported operating systems the warning has been removed from the installer.

Problem: The ClearCase context menu in Windows Explorer is missing after an upgrade to version 9.0.1.4.

Fix: The ClearCase context menu in Windows Explorer has been restored.

Problem: Using the UCM/CQ integration Find activities operation unusable on ClearTeam Explorer CCCQ UCM with local views.

Fix: The fix involved adding handling of the login to distinguish properly between the ClearCase and ClearQuest providers at login time.

Problem:The ClearCase "cleartool catcs" command, piped to another process (ex: cleartool catcs | head ) may fail.

Fix: The "cleartool catcs" signal handler was repaired.

Problem: cleartool mkbl -ddepends can generate a misleading error message if a component being dropped is not in the configuration for the specified stream.

Fix: An additional warning will be printed informing the user that a component can not be found in a baseline.

Problem: CAL applications may crash (after ClearCase 9.0) due to memory corruption.

Fix: CAL was fixed to properly report "owner" and "group" values without corrupting memory.

Problem: The ClearCase "cleartool catcs" command, piped to another process (ex: cleartool catcs | head ) may fail.

Fix: The "cleartool catcs" signal handler was repaired.

Problem: When you are installing the 9.0.1.1 Eclipse plug-in for Rational ClearTeam Explorer, you may find that the version string displays 9.0.0.xxx instead of 9.0.1.xxxx.

Fix: The version string was fixed.

Problem: ClearCase creates R: drive as a network drive, but the network provider did not recognize it as a network resource it manages. Windows Explorer used to receive errors when trying to get the universal name of such a drive and failed to search files on it.

Fix: The network provider was changed to recognize automatic views as a network resource it manages.

Problem: Documentation missing on maximum MVFS scaling factor on Windows.

Fix: The online help has been updated to include the maximum value MVFS scaling factor on Windows

Problem: The "Make Baseline" dialog in ClearTeam Explorer has a "Scope" tab. This allows the baseline creation to be restricted to "Selected Components". Selecting only a component where no actual changes have been made causes a baseline to be created in a component that has had changes made, but was not selected.

Fix: The fix corrects the method to retrieved selected components in the component list.

Problem: If VOB or Component is added outside of CTE then CTE load rules doesn't show newly added VOB or Component unless and until CTE is restarted.

Fix: A "refresh button" has been added in CTE load rules dialog.

Problem: CAL applications may crash (after ClearCase 9.0) due to memory corruption.

Fix: CAL was fixed to properly report "owner" and "group" values without corrupting memory.

Problem: rcleartool lsproject was requiring a "project:" selector prefix when it should not have been needed.

Fix: The rcleartool lsproject command now works correctly without a "project:" prefix.

Problem: cleartool or other client programs using integrations such as Cadence Design Framework or CtCmd perl package could get errors communicating with a VOB database server if the network connection closes unexpectedly or the db_server exits prematurely. Those errors could persist and repeat multiple times.

Fix: ClearCase has been fixed to detect the network errors and, when possible to do safely, restart transactions with the VOB database

Problem: Not able to add load rules having spaces in snapshot and web views.

Fix: Load rule having spaces will be added automatically in double quotes.

August 9 2018

Superseded

Problem: When an IBM Rational ClearCase Unified Change Management (UCM) deliver is in progress and that view is inaccessible, starting a second deliver from a different view on the same streams will allow you to reset the original deliver but will not give any information about the view that started the original deliver.

Fix: ClearCase UCM deliver will now give information about the view that started the original delivery.

Problem: ClearCase triggers firing on deliver_cancel and rebase_cancel are not working as designed in CCRC.

Fix: ClearCase triggers will now work on deliver_cancel and rebase_cancel.

Problem: The ClearQuest API GetEnabledEntityDefs can return a null value if there are no entity defs selected by the call. It should return an empty set of entitydefs instead. This can cause performance and other problems for consumers of the API such as CQ Web, especially if the ClearQuest database table ownership was not configured correctly.

Fix: The ClearQuest API GetEnabledEntityDefs now returns an empty set of entitydefs in all cases when there are no entitydefs returned by the call.

Problem: On a Solaris 11 system, the ClearCase VOB mount limit was being incorrectly calculated, and so if a very large number of VOBs is concurrently mounted, one of two different symptoms may occur. A cleartool mount command may fail, with the message "mount: file table overflow", or, a system crash may occur, with the error "device number too big for fsid!" in the system messages log.

Fix: The VOB mount limit for Solaris 11 is being correctly calculated.

Problem: ClearCase MVFS used the same locking resource to protect the file disposition flag and the cache state. When a process tried to delete a file with its cache enabled, it acquires a lock to set the file disposition and send a call to the view server. The view server will open the cleartext file and cause the cache to become invalid, this would cause the lock to be acquired again to update the cache state, but the lock is never acquired.

Fix: Because file disposition does not deal with the actual file content, an exclusive locking resource has been created to protect the cache state, so that the file disposition can be changed regardless of the cache state.

Problem: Corrupted ClearCase view databases could be treated as valid.

Fix: Fixes issues where corrupt view databases could be treated as valid.

Problem: When you are working in the Rational ClearCase/Microsoft Visual Studio 2017 Integration, you may find that the solution files are not handled correctly.

Fix: The integration was fixed to properly handle solution files.

Problem: A ClearCase database incompatibility was introduced for UCM PVOBs on Windows between versions 9.0.1.0 and 9.0.1.1.

Fix: This fixes a database compatibility issue introduced on Windows PVOBs between version 9.0.1.0 and 9.0.1.1. With this fix, databases created on version 9.0.1.0 are now compatible.

Problem: In ClearCase ClearTeamExplorer (CTE) the paths shown in the pending changes view may sometimes be incorrect specially when there are major similarities between directory names in the VOB root directory. For example "/vob/a" and "/vob/ab".

Fix: The fix addresses the path display issue in ClearTeam Explorer's Pending Changes view.

Problem: Certain sequences of ClearCase UCM baseline operations could cause a segmentation violation.

Fix: This fixes a possible segmentation violation during ClearCase UCM baseline operations.

Problem: Under certain circumstances, ClearCase omake does not properly handle memory allocation errors and was not freeing up no longer used memory.

Fix:  ClearCase omake was modified to correct one scenario to now exit in the event of a memory allocation error, and was also modified to free up memory for one scenario when the memory is no longer needed.

Problem:ClearCase clearmake, in an automatic view, incorrectly attempts to contact a VOB looking for derived objects to re-use.

Fix: ClearCase clearmake was modified to skip checking for derived objects when an automatic view is used.

Problem:ClearCase clearmake may run out of memory when a make file contains a large number of macros.

Fix: Changes were made to do a better job of freeing up memory when the memory was no longer required and this will allow clearmake to better handle makefiles with a large number of macros.

Problem: MultiSite syncreplica import will occasionally fail with "Segmentation Fault" for a mkbaseline oplog having a nonzero value for the num_reorder_ents field.

Fix: MultiSite syncreplica import will no longer fail with "Segmentation Fault" for such an oplog.

Problem: A MultiSite syncreplica -import may fail on an rmver oplog with the error "string buffer too small."

Fix: Importing an rmver oplog should no longer hit this error.

Problem: The Rational Software Architect ClearCase Remote Client extension integration allows model files to be removed using the "Delete" key from the RSA workspace. This should not be allowed in this perspective and is blocked in the GUI context menu.

Fix: With this change when Delete key is pressed with multiple selections, the Delete Action will be triggered only for non-model files. On the GUI context menu, the current functionality is retained. On the context menu of multiple selection, if the selection contains at least one model file, then Remove option is disabled.

Nov 15 2018

Superseded

Problem: ClearCase search's result pane was not getting updated post the SCM operations.

Fix: The fix ensures ClearCase search's result pane is accurately updated post any SCM operation ensuring a correct search result the second time.

Problem: CM Server when looking up a view by its uuid was not allowing for case where operation completed successfully but did not find any views.

Fix: CM Server will now correctly return a "not found" status when the error situation is encountered.

Problem: System may panic when accessing view-extended pathnames.

Fix: ClearCase's MVFS filesystem was update to handle non-vob view extended pathname.

Problem: Automatic views on Windows could be corrupted if they were active at the time of a user logoff or system shutdown.

Fix: Automatic views now cleanly shut down during a user logoff or system shutdown

Problem: A bug in the AIX operating system causes call to getgrgid_r()    to incorrectly report status when a group doesn't fit in a 64k buffer.

Fix: Status checking was extended to catch the need to extend the buffer used to contain the members of a large group.

Problem: "Create View" dialogue in CTE can indicate incorrect view types as being available for creation. When client and server are on same machine, selection of UCM Vob Tag, UCM Projects and UCM Project under local and server node are not working correctly. I.e If we select Vob Tag under local and then we select the same under server node, selection is not changing.

Fix: Post fix, it will provide right option in create view dialogue, based on node we selected. If It is local, it will provide option of Dynamic and Snapshot, and If It is server node, will provide option of Web and Automatic view(If support is there) option.

Problem: ClearCase users running Linux may see EMLINK ("Too many links") errors when trying to access directories.

Fix: The EMLINKS error returned by MVFS was replaced by a preventive code that avoids occurrences of multiple entries.

Problem: The 32 and 64 bit Linux versions of ClearCase are intended to be binary database compatible. This is an issue where trigger definitions are not binary compatible. See http://www.ibm.com/support/docview.wss?uid=swg22004783 for more details.

Fix: This fixes the trigger incompatibility between 32 and 64 bit versions of ClearCase.

Problem: Failing preop mkbl triggers still allow VOB modification.

Fix: Failing preop mkbl triggers can now properly block VOB modification.

Problem: Web view load/update fails with an error: java.lang.IllegalArgumentException: null incase ccrcSupportsParallelLoad is enabled and ccrcMaxRequestsPerSession <= 3.

Fix: When ccrcSupportsParallelLoad is enabled and ccrcMaxRequestsPerSession <= 3, parallel operations will be disabled and below mentioned message will be displayed to customer in a message box : "ccrcMaxRequestsPerSession as defined is too low, therefore parallel operations will be disabled. To enable parallel operations for web views, define ccrcMaxRequestsPerSession with a setting of 4 or higher."

Problem: Installation of the ClearCase CCRC WAN Server is failing to load into WebSphere on non-English operating systems.

Fix: The installation process was expecting the output of the managesdk command to be in English. This was not the case on a non-English operating system. The installation has been fixed to correctly parse the non-English output.

Problem: Certain features in the CTE eclipse update site clash with previously installed features in the desktop products such as IDA and RSA.  This prevents the capability to install CTE via the update site into these eclipse-based products.

Fix: Changes have been made to the update site feature.xml for the CTE IDE feature that will allow the remainder of CTE to be installed if the required features and plugins that support the CTE IDE have already been installed.

Problem: Files of size > 2GB, fails to load in web view.

Fix: After fix, files of size >2GB are getting loaded in Web view.

Problem: Shortkeys CTRL+C(Copy), CTRL+X(Cut), CTRL+V(Paste) were not functional in ClearTeam Explorer standalone client.

Fix: Post the fix, CTRL+C(Copy), CTRL+X(Cut), CTRL+V(Paste) are supported and functional in ClearTeam Explorer standalone client.

Problem: When using the ClearTeam Explorer extension with Rational Application developer the 'Last Modified' and 'Created' fields in the details view will not have valid data.

Fix: The fields now display correct data.

Problem: Customer may be seeing the root  ClearCase MVFS(Multi Version File System ) path with a double backslash at the end of the path when using net use command.

Fix: ClearCase Network Provider was changed to avoid this behavior.

18 December 2017

Superseded

Problem: For base ClearCase VOBs using the CMI integration, findmerge -avobs fails when two or more VOBs have elements that require merging.

Fix: The findmerge -avobs command should work properly for multiple VOBs using the CMI integration.

Problem: ClearCase reop triggers do not block the request for mastership in synchronous request for mastership checkouts and mkelems.

Fix: Preop triggers on reqmaster will now fire during synchronous request for mastership checkouts and mkelems, and will allow the User to block requests for mastership during those operations.

Problem: In ClearTeam Explorer, the graphical version tree would not display the view-selected version correctly if the element name contained @@ (version-extended characters) in the middle of the name.

Fix: ClearTeam Explorer is fixed to display the view-selected version correctly when an element name contains @@ (version-extended characters) in the middle of the name. Note that using the version-extended characters at the end of an element name is not supported in ClearCase.

Problem: The scroll bar in missing in ClearCase ClearTeam Explorer (CTE) version tree for some versions of elements that have a large number of labels.

Fix: The missing scrollbar issue has been fixed.

Problem: ClearCase users with certain special characters in their password such as: an UMLAUT cannot successfully create an automatic view owing to rview agent failing to log into the server.

Fix: The rview agent now is capable of properly logging into cmserver using the user's credentials even if they have the afore mentioned special characters.

Problem: When ClearCase server-side group substitution is enabled, and a user whose UID is not mappable to a username and set of groups attempts to access a view, the view_server emits many log messages about the unmapped user such as "No group list for uid 12345"

Fix: When an unknown user accesses ClearCase, the log messages about their account are classified as warnings and are rate-limited to once per user per cache lifetime interval.

Problem: ClearCase Windows clients get errors when communicating with Solaris SPARC VOB or view servers, similar to this: credmap_lookup_whole_string_credentials call failed: RPC: Server can't decode arguments This occurs when both the client and server are running one of these ClearCase releases: 9.0.0.4, 9.0.0.5, 9.0.1, or 9.0.1.1

Fix: The VOB and view servers have been fixed to work correctly with Windows clients

Problem: While using a ClearCase dynamic view directory reading operations for directories with many elements may take longer than necessary.

Fix: MVFS was changed to use all the data provided by the view server for directory enumerations.

Problem: Attempts to rebuild ClearCase MVFS on Ubuntu 14.04 with kernel 3.13.0-132 result in build error.

Fix: MVFS source code was changed to be compatible with kernel 3.13.0-132.

Problem: As a result of changes to simplify the procedure for rebuilding the ClearCase MVFS kernel module on Linux, the instructions in /var/adm/rational/clearcase/mvfs/mvfs_src/README.txt are incorrect.

Fix: The /var/adm/rational/clearcase/mvfs/mvfs_src/README.txt has been updated.

Problem: When using ClearCase clients to access a VOB hosted on a different operating system type (one side is Windows, the other is UNIX/Linux), identities for VOB objects may show up with the server's identities instead of being mapped to the client's identities.

Fix: The ClearCase client has been fixed to properly map VOB object identities to the local operating system's identities.

Problem: The ClearCase xcleardiff gui does not display color options correctly in ClearCase 8.0.x running on Linux

Fix: Color management has been corrected.

Problem: A ClearCase Windows may crash when accessing dynamic views created with -host, -gpath (also PI66371)

Fix: ClearCase was changed to avoid -host, -gpath and -hpath to be used on a non-NAS environment.

Problem: When using Visual Studio with projects in an ClearCase automatic view, accessed using a subst'd path in the same way one would with dynamic views, Visual Studio does not recognize the artifacts in the project as being under source control.

Fix: The integration has been enhanced to work with subst'd automatic view roots.  The subst must be of the form: X:\ -> R:\view_tag\

Problem: When using the ClearTeam Explorer extension with Rational Application developer the 'Last Modified' and 'Created' fields in the details view will not have valid data.

Fix: The fields now display correct data.

Problem: When opening a solution that is under Source Control from Windows Explorer or ClearCase Explorer an error is shown saying "The source control provider associated with this solution could not be found. The projects will be treated as not under source control. Do you want to permanently remove the source control bindings from this project?"

Fix: This issue has been fixed.

Problem: Customer may be seeing the root  ClearCase MVFS(Multi Version File System ) path with a  double backslash("\\"") at the end of the path when using net use command.

Fix: ClearCase Network Provider was changed to avoid this behavior.

13 September 2017

Superseded

Problem: File operations on ClearCase dynamic views can cause the appearance of D-state process.

Fix: MVFS was changed to detect and prevent the error condition that makes the D-state process occurrence.

Problem: The ClearCase db_server processes can behave erratically if single token lines are placed in the db.conf file.

Fix: The db_server processes properly parse single token lines in the db.conf file.

Problem: Checkout and other operations in an automatic view hosted on a Solaris SPARC host could fail with errors similar to this: CRMAP7009: Command "CCW_CCase::checkout_rpc" failed: Error: "CRMAP7009: Command: "rview_agent command" failed: 20001: Operation "ns_readdir_ext" failed: error detected by ClearCase Subsystem." and leave the automatic view corrupted.

Fix: The CCRC WAN server on Solaris SPARC has been fixed to work correctly for checkout and other operations.

Problem: ClearCase view private files larger than 4 KB take more time to read on SUSE SLES 12 SP2 when compared to SUSE SLES 11 SP3.

Fix:MVFS was fixed to make the read-ahead work correctly on SUSE SLES 12. logged.

Problem: Attempting to connect to the ClearCase CCRC WAN server will fail if the user account is numeric only.

Fix: Numeric only user accounts now correctly connect.

Problem: ClearCase processes crash when executed by a Windows account that is a member of a group represented by long Windows SID, such as SIDs for non-domain accounts linked to a Microsoft account 

Fix: ClearCase processes no longer fail with such accounts, but ClearCase will ignore any group (behave as if the user is not a member of the group)  represented by a long Windows SID.

Problem: The outdated Microsoft Visual Studio 2005 Visual C++ runtimes are distributed with ClearCase and ClearQuest as those products have components that depend on them.

Fix: All dependencies on the Microsoft Visual Studio 2005 Visual C++ runtimes have been removed from ClearCase and ClearQuest, and those runtimes are no longer installed

Problem: When exporting a view and VOB path for non-ClearCase access from a RedHat Linux server, applications on the client side may experience access denied or similar errors.

Fix: Necessary permission override checks were added to properly handle the root user id for access, rather than blocking the remote access for root.

Problem: ClearCase clearmrgman dumps core when performing "checkin".

Fix: The clearmrgman cleanup handler has been fixed.

Problem: The ClearCase clearmake utility (on UNIX/Linux platforms) could stall waiting for a child build process to complete, even when the child process has actually finished and exited.

Fix: Clearmake now periodically checks for pending child build processes to confirm if they are still running, and to proceed with the remainder of the build if they have completed.

Problem: ClearCase customers may experience a system crash when accessing MVFS files.

Fix: This issue has been resolved.

Problem: A ClearCase Syncreplica -import of the modstream_cspec oplog generated by creating a child stream fails with a segmentation fault in a sibling that has removed the parent stream.

Fix: The replay code has been modified to properly store the modstream_cspec oplog while skipping its replay if the parent stream is not found in the importing replica.

Problem: The ClearCase "xclearcase" or "xlsvtree" graphical interfaces (on Linux hosts) will hang when started with an invalid path.

Fix: ClearCase exit handling code was fixed.

Problem: A ClearCase "RMSTREAM" of "Feature Level 5" stream after raising VOB to "Feature Level 7" FAILS WITH "ERROR FROM VOB DATABASE" FOR UCM PROJECT VOB.

Fix: Feature Level 7 VOBs now can handle "rmstream" command from Feature Level 5.

Problem: An attempt to rebuild the MultiVersion File System kernel module for IBM ClearCase will fail on SUSE SLES12 SP2 and Ubuntu 16.04 systems with the error message: /var/adm/rational/clearcase/mvfs/mvfs_src/mvfs_mdep_linux.c:2764:9: error: implicit declaration of function  inode_capable  [-Werror=implicit-function-declaration]

Fix: This problem has been resolved.

Problem: When running ClearCase SLES 12 SP2, you may observe repetitive messages such as this in the syslog: systemd[16300]: Failed to get udev device from devnum 253:0: No such device

Fix: The ClearCase MVFS has been updated to provide the information which systemd is querying in this situation, to eliminate the log messages.

Problem: ClearCase customers are unable to use dynamic views because MVFS is not loaded on Windows 10 if Device Guard is enabled.

Fix: The ClearCase MVFS driver was changed to adopt the requirements imposed by Device Guard.

Problem: When attempting to build the ClearCase MultiVersion Filesystem (MVFS) as part of installing ClearCase on a SuSE 12 SP2 host, the MVFS will not build successfully.

Fix: A problem which caused errors when rebuilding the ClearCase MVFS on SuSE 12 SP2 systems was fixed.

Problem:Removing a ClearCase UCM stream while a remote site has a view attached (to the stream) causes the db dumper to fail.

Fix: The db dumper has been fixed.

Problem: The ClearCase UCM/ClearQuest integration was creating multiple ClearQuest web sessions when using ClearTeam Explorer with a web-based view.

Fix: The UCM/ClearQuest integration now uses fewer ClearQuest web sessions when using ClearTeam Explorer with a web-based view.

Problem: A user is unable to connect to a ClearCase Remote Client WAN server, if the login URL contains a trailing  white space.

Fix: Trailing white space is now removed from URLs in all cases.

Problem:ClearCase users cannot create or use automatic views if the "http_proxy" environment variable is set.

Fix: Automatic views now work using direct connections to the CCRC WAN server even when the "http_proxy" environment variable is set. NOTE:  Automatic views do not support proxies, even if ClearTeam Explorer is configured to use proxies.

Problem: Intermittently a ClearCase shipping_server may hang after executing a shipping order or during syncreplica -export -fship

Fix: The shipping_server will now complete its actions without hanging.

Problem: As documented in ClearCase technote 1259280, accessing non-VOB files using a view-extended pathname on Linux kernels after 2.4.18 is not supported due to kernel limitations.  However, on some kernels, this may cause a system crash.

Fix: The non-VOB pathname access using a view-extended pathname is still not supported, but ClearCase has been updated so that these references will not cause a system crash.

Problem: In a relatively rare configuration of NFS (/net not being used for the automounts, but used for view storage)  the ClearCase rmview command will pause for 30 seconds as it waits for all the files in the view_storage to no longer be accessible.  Aggressive NFS directory caching by the AIX OS is responsible for this.

Fix: The NFS cached directory contents are explicitly flushed prior to removing view storage, thus avoiding the 30 second pause on rmview.   This fix is for AIX only.

Problem: A ClearCase checkout using the ctcmd.pm module fails with an abort.

Fix: A ClearCase checkout using the ctcmd.pm module no longer aborts.

Problem: Rational ClearCase/Cadence integration menu customizations do not load properly after upgrading to ClearCase 8.0.1.13

Fix: The menu customization issue is resolved.

Problem: Missing a semi-colon in the moving a view command.

Fix: Help topic updated to include the missing semi-colon in the moving a view command.

Problem: ClearTeam Explorer can produce the following error when attempting a directory merge when in a webview: "As a result of a directory merge operation, one or more resources, requiring a merge, have been removed"

Fix: A directory merge in a webview will no longer result in the error.

Problem: Users of ClearCase dynamic views may see messages reporting stale transaction ids in the mvfs_log log file. Unexpected application I/O errors or hangs may coincide with these messages.

Fix: The logic for how the MVFS handles certain transient errors in communicating with a view_server process has been corrected.

Problem: More detail needed in "Synchronization of identities and permissions information" help topic

Fix: Help topic updated to when include information about a replica exports sync packets.

Problem: The ClearCase web-based UCM/ClearQuest integration was unable to work on ClearQuest records that contained security contexts where the user was not a member of one or more of those contexts.

Fix:The web-based UCM/CQ integration can now work on ClearQuest records that contain security contexts where the user is not a member of one or more of those contexts.

Problem:Creating or deleting hyperlinks that span VOBs (common in a UCM setup) in IBM Rational ClearCase can lead to a situation where two processes are waiting on each other for a lock on one of the VOB databases. This will lead to the Dead Man Lock Timeout to be triggered, making one of the two operations to fail.

Fix: A ClearCase db transaction will be suspended and restarted for cross vob hlinks.

Problem: The ClearCase mkview command creates UCM views with 'SHAREABLE_DOS' property, ignoring the site setting.

Fix: Help topic updated in IBM Knowledge Center.

Problem: When searching for files in a ClearCase dynamic view, using the Windows Explorer Search feature, you may not see any results.

Fix: Changes were made on ClearCase Network Provider to return correct path information.

Problem: When mounting a ClearCase VOB on some versions of Linux (Red Hat Enterprise Linux 7.x, SUSE Linux 12.x, Ubuntu Linux 16.04), the mount will succeed, but a warning will be displayed: "mount.mvfs: Warning: unable to open mount table".

Fix: The ClearCase VOB mount code has been updated so that the system mount table is updated correctly on versions of Linux where it is virtual, rather than a file /etc/mtab.  With this fix, the warning message is eliminated.

Problem: When performing audited builds in IBM Rational ClearCase dynamic views on Microsoft Windows, the audit record may not be complete.

Fix: Changes were made to correct the auditing of non-cached reads.

Problem: When using the Rational ClearCase File Service (CCFS) as the interoperability solution to access Unix-hosted VOBS from Windows you may encounter a "Permission denied " error.

Fix: Windows now skips permission denied ports.

Problem: When using a makefile to overwrite a file using the move command in a ClearCase Dynamic View you may notice that the source file was not removed.

Fix: ClearCase Multi Version File System was changed to enable winked-in files to be overwritten on move operations.

Problem: The ClearCase Unix version tree browser dumps core when the zoom control was used to shrink the version tree.

Fix: The Unix version tree browser has been fixed.

15-June 2017

Superseded

Problem: When searching for files in a ClearCase dynamic view, using the Windows Explorer Search feature, you not see any results.

Fix: Changes were made on ClearCase Network Provider to return correct path information.

Problem: MKVIEW creates UCM views with 'SHAREABLE_DOS' property, ignoring the site setting. .

Fix: Help topic updated in IBM Knowledge Center.

Problem: Deleting and walk through cross vob hlink can cause database dead lock. .

Fix: Help topic updated in IBM Knowledge Center.

Problem: More detail needed in "Synchronization of identities and permissions information" help topic.

Fix: Help topic updated to when include information about a replica exports sync packets.

Problem: Missing a semi-colon in the moving a view command.

Fix: Help topic updated to include the missing semi-colon in the moving a view command.

Problem: Menu customizations do not load properly after upgrading to ClearCase 8.0.1.13.

Fix: The menu customization issue is resolved.

Problem: ClearCase checkout using the ctcmd.pm module fails with an abort.

Fix: ClearCase checkout using the ctcmd.pm module no longer aborts.

Problem: In a relatively rare configuration of NFS (/net not being used for the automounts, but used for view storage) the rmview command will pause for 30 seconds as it waits for all the files in the view_storage to no longer be accessible. Aggressive NFS directory caching by the AIX OS is responsible for this.

Fix: The NFS cached directory contents are explicitly flushed prior to removing view storage, thus avoiding the 30 second pause on rmview. This fix is for AIX only.

Problem: As documented in ClearCase technote 1259280, accessing non-VOB files using a view-extended pathname on Linux kernels after 2.4.18 is not supported due to kernel limitations.  However, on some kernels, this may cause a system crash.

Fix: The non-VOB pathname access using a view-extended pathname is still not supported, but ClearCase has been updated so that these references will not cause a system crash.

Problem: Intermittently a shipping_server may hang after executing a shipping order or during syncreplica -export -fship

Fix: The shipping_server should complete its actions without hanging.

Problem: Users cannot create or use automatic views if the "http_proxy" environment variable is set.

Fix: Automatic views now work using direct connections to the CCRC WAN server even when the "http_proxy" environment variable is set. NOTE:  Automatic views do not support proxies, even if ClearTeam Explorer is configured to use proxies.

Problem: Evidently there were code paths where white space was not being trimmed.

Fix: Trailing white space is now removed from URLs in all cases

Problem: The UCM/ClearQuest integration was creating multiple ClearQuest web sessions when using ClearTeam Explorer with a web-based view.

Fix: The UCM/ClearQuest integration now uses fewer ClearQuest web sessions when using ClearTeam Explorer with a web-based view.

Problem: Removing UCM stream while in remote site there is a view attached. The db dumper will fail.

Fix: Update db dumper to replace the missing stream id to a NULL and continue.

Problem: An attempt to rebuild the MultiVersion File System kernel module for IBM ClearCase will fail on SUSE SLES12 SP2 and Ubuntu 16.04 systems with the error message: /var/adm/rational/clearcase/mvfs/mvfs_src/mvfs_mdep_linux.c:2764:9: error: implicit declaration of function  inode_capable  [-Werror=implicit-function-declaration]

Fix: This problem has been fixed in ClearCase release 9.0.1.

Problem: "RMSTREAM" of "Feature Level 5" stream after raising VOB to "Feature Level 7" fails with "ERROR FROM VOB DATABASE" for UCM project VOB.

Fix: Feature Level 7 VOB now can handle "rmstream" command from Feature Level 5.

Problem: Syncreplica -import of the modstream_cspec oplog generated by creating a child stream fails with a segmentation fault in a sibling that has removed the parent stream.

Fix: The replay code has been modified to properly store the modstream_cspec oplog while skipping its replay if the parent stream is not found in the importing replica.

Problem: Customers may experience a system crash when accessing MVFS files.

Fix: There was a not initialized structure being released, making the system to crash. The structure is now being appropriately initialized and the issue does not occur anymore.

18 December 2017

Current

Problem: For base ClearCase VOBs using the CMI integration, findmerge -avobs fails when two or more VOBs have elements that require merging.

Fix: The findmerge -avobs command should work properly for multiple VOBs using the CMI integration.

Problem: ClearCase reop triggers do not block the request for mastership in synchronous request for mastership checkouts and mkelems.

Fix: Preop triggers on reqmaster will now fire during synchronous request for mastership checkouts and mkelems, and will allow the User to block requests for mastership during those operations.

Problem: In ClearTeam Explorer, the graphical version tree would not display the view-selected version correctly if the element name contained @@ (version-extended characters) in the middle of the name.

Fix: ClearTeam Explorer is fixed to display the view-selected version correctly when an element name contains @@ (version-extended characters) in the middle of the name. Note that using the version-extended characters at the end of an element name is not supported in ClearCase.

Problem: The scroll bar in missing in ClearCase ClearTeam Explorer (CTE) version tree for some versions of elements that have a large number of labels.

Fix: The missing scrollbar issue has been fixed.

Problem: ClearCase users with certain special characters in their password such as: an UMLAUT cannot successfully create an automatic view owing to rview agent failing to log into the server.

Fix: The rview agent now is capable of properly logging into cmserver using the user's credentials even if they have the afore mentioned special characters.

Problem: When ClearCase server-side group substitution is enabled, and a user whose UID is not mappable to a username and set of groups attempts to access a view, the view_server emits many log messages about the unmapped user such as "No group list for uid 12345"

Fix: When an unknown user accesses ClearCase, the log messages about their account are classified as warnings and are rate-limited to once per user per cache lifetime interval.

Problem: ClearCase Windows clients get errors when communicating with Solaris SPARC VOB or view servers, similar to this: credmap_lookup_whole_string_credentials call failed: RPC: Server can't decode arguments This occurs when both the client and server are running one of these ClearCase releases: 9.0.0.4, 9.0.0.5, 9.0.1, or 9.0.1.1

Fix: The VOB and view servers have been fixed to work correctly with Windows clients

Problem: While using a ClearCase dynamic view directory reading operations for directories with many elements may take longer than necessary.

Fix: MVFS was changed to use all the data provided by the view server for directory enumerations.

Problem: Attempts to rebuild ClearCase MVFS on Ubuntu 14.04 with kernel 3.13.0-132 result in build error.

Fix: MVFS source code was changed to be compatible with kernel 3.13.0-132.

Problem: As a result of changes to simplify the procedure for rebuilding the ClearCase MVFS kernel module on Linux, the instructions in /var/adm/rational/clearcase/mvfs/mvfs_src/README.txt are incorrect.

Fix: The /var/adm/rational/clearcase/mvfs/mvfs_src/README.txt has been updated.

Problem: When using ClearCase clients to access a VOB hosted on a different operating system type (one side is Windows, the other is UNIX/Linux), identities for VOB objects may show up with the server's identities instead of being mapped to the client's identities.

Fix: The ClearCase client has been fixed to properly map VOB object identities to the local operating system's identities.

Problem: The ClearCase xcleardiff gui does not display color options correctly in ClearCase 8.0.x running on Linux

Fix: Color management has been corrected.

Problem: A ClearCase Windows may crash when accessing dynamic views created with -host, -gpath (also PI66371)

Fix: ClearCase was changed to avoid -host, -gpath and -hpath to be used on a non-NAS environment.

Problem: When using Visual Studio with projects in an ClearCase automatic view, accessed using a subst'd path in the same way one would with dynamic views, Visual Studio does not recognize the artifacts in the project as being under source control.

Fix: The integration has been enhanced to work with subst'd automatic view roots.  The subst must be of the form: X:\ -> R:\view_tag\

Problem: When using the ClearTeam Explorer extension with Rational Application developer the 'Last Modified' and 'Created' fields in the details view will not have valid data.

Fix: The fields now display correct data.

Problem: When opening a solution that is under Source Control from Windows Explorer or ClearCase Explorer an error is shown saying "The source control provider associated with this solution could not be found. The projects will be treated as not under source control. Do you want to permanently remove the source control bindings from this project?"

Fix: This issue has been fixed.

Problem: Customer may be seeing the root  ClearCase MVFS(Multi Version File System ) path with a  double backslash("\\"") at the end of the path when using net use command.

Fix: ClearCase Network Provider was changed to avoid this behavior.

13 September 2017

Superseded

Problem: File operations on ClearCase dynamic views can cause the appearance of D-state process.

Fix: MVFS was changed to detect and prevent the error condition that makes the D-state process occurrence.

Problem: The ClearCase db_server processes can behave erratically if single token lines are placed in the db.conf file.

Fix: The db_server processes properly parse single token lines in the db.conf file.

Problem: Checkout and other operations in an automatic view hosted on a Solaris SPARC host could fail with errors similar to this: CRMAP7009: Command "CCW_CCase::checkout_rpc" failed: Error: "CRMAP7009: Command: "rview_agent command" failed: 20001: Operation "ns_readdir_ext" failed: error detected by ClearCase Subsystem." and leave the automatic view corrupted.

Fix: The CCRC WAN server on Solaris SPARC has been fixed to work correctly for checkout and other operations.

Problem: ClearCase view private files larger than 4 KB take more time to read on SUSE SLES 12 SP2 when compared to SUSE SLES 11 SP3.

Fix:MVFS was fixed to make the read-ahead work correctly on SUSE SLES 12. logged.

Problem: Attempting to connect to the ClearCase CCRC WAN server will fail if the user account is numeric only.

Fix: Numeric only user accounts now correctly connect.

Problem: ClearCase processes crash when executed by a Windows account that is a member of a group represented by long Windows SID, such as SIDs for non-domain accounts linked to a Microsoft account 

Fix: ClearCase processes no longer fail with such accounts, but ClearCase will ignore any group (behave as if the user is not a member of the group)  represented by a long Windows SID.

Problem: The outdated Microsoft Visual Studio 2005 Visual C++ runtimes are distributed with ClearCase and ClearQuest as those products have components that depend on them.

Fix: All dependencies on the Microsoft Visual Studio 2005 Visual C++ runtimes have been removed from ClearCase and ClearQuest, and those runtimes are no longer installed

Problem: When exporting a view and VOB path for non-ClearCase access from a RedHat Linux server, applications on the client side may experience access denied or similar errors.

Fix: Necessary permission override checks were added to properly handle the root user id for access, rather than blocking the remote access for root.

Problem: ClearCase clearmrgman dumps core when performing "checkin".

Fix: The clearmrgman cleanup handler has been fixed.

Problem: The ClearCase clearmake utility (on UNIX/Linux platforms) could stall waiting for a child build process to complete, even when the child process has actually finished and exited.

Fix: Clearmake now periodically checks for pending child build processes to confirm if they are still running, and to proceed with the remainder of the build if they have completed.

Problem: ClearCase customers may experience a system crash when accessing MVFS files.

Fix: This issue has been resolved.

Problem: A ClearCase Syncreplica -import of the modstream_cspec oplog generated by creating a child stream fails with a segmentation fault in a sibling that has removed the parent stream.

Fix: The replay code has been modified to properly store the modstream_cspec oplog while skipping its replay if the parent stream is not found in the importing replica.

Problem: The ClearCase "xclearcase" or "xlsvtree" graphical interfaces (on Linux hosts) will hang when started with an invalid path.

Fix: ClearCase exit handling code was fixed.

Problem: A ClearCase "RMSTREAM" of "Feature Level 5" stream after raising VOB to "Feature Level 7" FAILS WITH "ERROR FROM VOB DATABASE" FOR UCM PROJECT VOB.

Fix: Feature Level 7 VOBs now can handle "rmstream" command from Feature Level 5.

Problem: An attempt to rebuild the MultiVersion File System kernel module for IBM ClearCase will fail on SUSE SLES12 SP2 and Ubuntu 16.04 systems with the error message: /var/adm/rational/clearcase/mvfs/mvfs_src/mvfs_mdep_linux.c:2764:9: error: implicit declaration of function  inode_capable  [-Werror=implicit-function-declaration]

Fix: This problem has been resolved.

Problem: When running ClearCase SLES 12 SP2, you may observe repetitive messages such as this in the syslog: systemd[16300]: Failed to get udev device from devnum 253:0: No such device

Fix: The ClearCase MVFS has been updated to provide the information which systemd is querying in this situation, to eliminate the log messages.

Problem: ClearCase customers are unable to use dynamic views because MVFS is not loaded on Windows 10 if Device Guard is enabled.

Fix: The ClearCase MVFS driver was changed to adopt the requirements imposed by Device Guard.

Problem: When attempting to build the ClearCase MultiVersion Filesystem (MVFS) as part of installing ClearCase on a SuSE 12 SP2 host, the MVFS will not build successfully.

Fix: A problem which caused errors when rebuilding the ClearCase MVFS on SuSE 12 SP2 systems was fixed.

Problem:Removing a ClearCase UCM stream while a remote site has a view attached (to the stream) causes the db dumper to fail.

Fix: The db dumper has been fixed.

Problem: The ClearCase UCM/ClearQuest integration was creating multiple ClearQuest web sessions when using ClearTeam Explorer with a web-based view.

Fix: The UCM/ClearQuest integration now uses fewer ClearQuest web sessions when using ClearTeam Explorer with a web-based view.

Problem: A user is unable to connect to a ClearCase Remote Client WAN server, if the login URL contains a trailing  white space.

Fix: Trailing white space is now removed from URLs in all cases.

Problem:ClearCase users cannot create or use automatic views if the "http_proxy" environment variable is set.

Fix: Automatic views now work using direct connections to the CCRC WAN server even when the "http_proxy" environment variable is set. NOTE:  Automatic views do not support proxies, even if ClearTeam Explorer is configured to use proxies.

Problem: Intermittently a ClearCase shipping_server may hang after executing a shipping order or during syncreplica -export -fship

Fix: The shipping_server will now complete its actions without hanging.

Problem: As documented in ClearCase technote 1259280, accessing non-VOB files using a view-extended pathname on Linux kernels after 2.4.18 is not supported due to kernel limitations.  However, on some kernels, this may cause a system crash.

Fix: The non-VOB pathname access using a view-extended pathname is still not supported, but ClearCase has been updated so that these references will not cause a system crash.

Problem: In a relatively rare configuration of NFS (/net not being used for the automounts, but used for view storage) the ClearCase rmview command will pause for 30 seconds as it waits for all the files in the view_storage to no longer be accessible. Aggressive NFS directory caching by the AIX OS is responsible for this.

Fix: The NFS cached directory contents are explicitly flushed prior to removing view storage, thus avoiding the 30 second pause on rmview.   This fix is for AIX only.

Problem: A ClearCase checkout using the ctcmd.pm module fails with an abort.

Fix: A ClearCase checkout using the ctcmd.pm module no longer aborts.

Problem: Rational ClearCase/Cadence integration menu customizations do not load properly after upgrading to ClearCase 8.0.1.13

Fix: The menu customization issue is resolved.

Problem: ClearTeam Explorer can produce the following error when attempting a directory merge when in a webview: "As a result of a directory merge operation, one or more resources, requiring a merge, have been removed"

Fix: A directory merge in a webview will no longer result in the error.

Problem: Users of ClearCase dynamic views may see messages reporting stale transaction ids in the mvfs_log log file.  Unexpected application I/O errors or hangs may coincide with these messages.

Fix: The logic for how the MVFS handles certain transient errors in communicating with a view_server process has been corrected.

Problem: The ClearCase web-based UCM/ClearQuest integration was unable to work on ClearQuest records that contained security contexts where the user was not a member of one or more of those contexts.

Fix:The web-based UCM/CQ integration can now work on ClearQuest records that contain security contexts where the user is not a member of one or more of those contexts.

Problem:Creating or deleting hyperlinks that span VOBs (common in a UCM setup) in IBM Rational ClearCase can lead to a situation where two processes are waiting on each other for a lock on one of the VOB databases. This will lead to the Dead Man Lock Timeout to be triggered, making one of the two operations to fail.

Fix: A ClearCase db transaction will be suspended and restarted for cross vob hlinks.

Problem: When searching for files in a ClearCase dynamic view, using the Windows Explorer Search feature, you may not see any results.

Fix: Changes were made on ClearCase Network Provider to return correct path information.

Problem: When mounting a ClearCase VOB on some versions of Linux (Red Hat Enterprise Linux 7.x, SUSE Linux 12.x, Ubuntu Linux 16.04), the mount will succeed, but a warning will be displayed: "mount.mvfs: Warning: unable to open mount table".

Fix: The ClearCase VOB mount code has been updated so that the system mount table is updated correctly on versions of Linux where it is virtual, rather than a file /etc/mtab.  With this fix, the warning message is eliminated.

Problem: When performing audited builds in IBM Rational ClearCase dynamic views on Microsoft Windows, the audit record may not be complete.

Fix: Changes were made to correct the auditing of non-cached reads.

Problem: When using the Rational ClearCase File Service (CCFS) as the interoperability solution to access Unix-hosted VOBS from Windows you may encounter a "Permission denied " error.

Fix: Windows now skips permission denied ports.

Problem: When using a makefile to overwrite a file using the move command in a ClearCase Dynamic View you may notice that the source file was not removed.

Fix: ClearCase Multi Version File System was changed to enable winked-in files to be overwritten on move operations.

Problem: The ClearCase Unix version tree browser dumps core when the zoom control was used to shrink the version tree.

Fix: The Unix version tree browser has been fixed.

15 March 2017

Superseded

Problem: File lock operations on ClearCase files when the view storage is NFS4 may result in error EBADF (Bad file number).

Fix: The Linux MVFS driver was modified to set the file access mode that can be accepted by NFS4.

Problem: Some xattr operations on ClearCase view or VOB files on SUSE Linux may cause D-STATE (zombies) processes.

Fix: ClearCase MVFS was changed to avoid acquiring the inode mutex for xattr operations.

Problem: Users of ClearCase on Oracle Solaris 11 may experience a system crash when using NFS-mounted remote VOB storage.

Fix: A defect in the ClearCase MVFS, which caused corruption of NFS data, has been fixed.

Problem: When working in ClearTeam Explorer (CTE) , you may find that the file you just checked out does not appear to be checked out only when the path is accessed through address bar.

Fix: Check out status is displayed as expected in ClearTeam Details pane, even when the file is accessed from the address bar.

Problem: ClearCase "chmaster -stream" may not change mastership of timeline objects.

Fix: On schema 80 and feature level 8, "chmaster -stream" will change mastership of timeline objects whether it has timeline folder or not.

Problem: ClearCase users may see intermittent Access Denied errors when accessing files using non-ClearCase Access if the VOB root directory does not have execute permissions set.

Fix: Capability checks have been added to the MVFS permission checks to resolve this situation.

Problem: On AIX 7.1, using the open() system call with the O_CLOEXEC flag to open a file/dir in the ClearCase MVFS returns EINVAL.

Fix: On AIX 7.1 (and later) the O_CLOEXEC flag can now be used to open a file/dir in the ClearCase MVFS.

Problem: In rare situations, ClearCase clearmake could hang when starting a child process to execute a build step.

Fix: ClearCase clearmake has been fixed to continue execution properly when starting child processes.

Problem: When a building in a ClearCase dynamic view, you may experience sporadic random read/write errors

Fix: This issue with IBM Rational ClearCase MVFS has been resolved.

Problem: The ClearCase binary_delta  type manager may not remove temporary file(s) after a failed type manager operation.

Fix:The ClearCase binary_delta  type manager was fixed to remove temporary files.

Problem: When using the ClearCase Remote Client command line interface -- rcleartool -- attempts to use rcleartool mkattr to create or update a string attribute may fail with 'invalid string "{passed string}"'.

Fix: Non-interactive invocations of rcleartool mkattr for string attributes no longer strips the embedded quotes and should apply the attribute properly.

Problem: When using the ClearCase Remote Client command line interface -- rcleartool -- attempts to use rcleartool mkattr to create or update a string attribute may fail with 'invalid string "{passed string}"'.

Fix: When automatically re-establishing a login session, a CTE, CMAPI or rcleartool client no longer consumes all the sessions available on a CCRC WAN server.

Problem: After writing to a file and closing it, if an application sets its attributes, ClearCase MVFS will change the attributes back to the values the file had when it was closed.

Fix: Before setting attributes after having a file changed and closed, MVFS now checks if the attributes has been set by an application and will persist it if so.

Problem: When building in an ClearCase dynamic view, you may experience a hang.

Fix: The lock acquisition rule has been fixed to resolve this specific case.

Problem: When using CtCmd with Rational ClearCase "cleartool describe -fmt" the output is truncated by one byte if the first string is 16384 characters and the second the second string is one byte longer than the first.

Fix: Cleartool describe buffer handling was fixed.

Problem: When performing audited builds in a ClearCase dynamic view the customer will see an "ACCESS DENIED" error log entry when deleting a derived object, although the delete operation completes successfully.

Fix: When a MVFS file is about to be deleted, MVFS tries to flush any pending change on the cache to its cleartext file, however derived object files are stored on a VOB, which are opened as read-only. Trying to flush files opened as read-only causes the "ACCESS DENIED" error seen on the log. Now MVFS only request a flush on such situation if the cleartext file is stored on a VIEW, and not on a VOB.

Problem: In a ClearCase nonpreserving replica with ACLs enabled, syncreplica replay of a mkelem oplog may generate a second "create file element" event in the database, which can cause failures in reformatvob and mkreplica -impor

Fix: The duplicate "create" event will no longer be generated.

7 December 2016

Supersededt

Problem: When running the ClearCase cleartool protectvob command against an ClearCase VOB stored over NFS, you may encounter an  error if the hostname of the storage device and the root of the NFS share are greater than 64 characters combined.

Fix: Faulty string manipulation has been corrected.

Problem: If a stream in a replicated UCM project VOB has "POLICY_CHSTREAM_UNRESTRICTED" enabled, then users at multiple sites are able to upgrade it to incrementally/fully labeled which causes multiple labels to be created/attached and the label status becomes "unavailable"

Fix: Mastership will be checked if POLICY_CHSTREAM_UNRESTRICTED is enabled.

Problem: When working in the ClearCase integration with Visual Studio 2015, you may find that the application crashes if you try to close a view private file that is either a .c or .h file in Visual Studio.

Fix: Faulty string manipulation has been fixed.

Problem: When using the Change Management Integration with ClearQuest some CMI provider errors were not appearing in the cmi_log and required tracing to properly debug.

Fix: CMI provider errors that were previously not appearing in the cmi_log are now properly logged.

Problem: When using the ClearCase/ClearQuest (CC/CQ) UCM integration through ClearQuest Web, there is a login error when trying to view a change set.

Fix: Change sets can now be viewed in ClearQuest Web using the CC/CQ UCM integration.

Problem: When working in the Rational ClearCase ClearTeam Explorer (CTE), you may find that doing a "merge to" in the CTE Version Tree will launch the Diffmerge GUI and will not detect the merge as a "trivial merge".

Fix: A new preference is introduced which will let the user control this behavior. And by default the merges from Version Tree will be done automatically. Preference location: Team->IBM Rational ClearTeam Explorer->Integration->Compare/Merge

Problem: ClearCase checkin failure due to a missing source container reports cleartext path.

Fix: The source container is now correctly included in the error message.

Problem: When you are working in the ClearCase and Visual Studio 2013 integration, you may find that the ClearCase context menu items are greyed out after performing your first ClearCase operation.

Fix: The CC-VS integration was not installed correctly, that has been fixed.

Problem: When using ClearTeam Explorer (CTE) and entering a directory for the first time, it can take a very long time to list the content. This is most visible if there is a huge number of files, symlinks or sub-directories.

Fix: There is improved performance especially when browsing parents with large number of symlinks underneath them.

Problem: When performing a distributed or parallel build using the ClearCase clearmake utility, the build may fail with automated build executor (abe) process errors.

Fix: Code that checks automated build executor (abe) process ids has been fixed.

Problem: In the ClearCase Knowledge Center, the ClearCase section Administering the CCRC WAN server > Configuring ClearQuest integration with ClearCase UCM topic states that: "A sample ClearQuest database map file that you can use as a template is installed here: clearcase_home/config/ccrc/ClearQuest-db-mapfile.conf.sample."

Fix: The correct statement is: "A sample ClearQuest database map file that you can use as a template is installed here: clearcase_home/config/ccrc/cq-db-mapfile.conf.sample."

Problem:When opening a Visual Studio (VS) project created without a solution file, the ClearCase (CC) plugin is not available in Visual Studio 2013-2015.

Fix: The CC-VS integration was not installed correctly, that has been fixed.

Problem: When mounting a ClearCase VOB on some versions of Linux (Red Hat Enterprise Linux 7.x, SUSE Linux 12.x, Ubuntu Linux 16.04), the mount will succeed, but a warning will be displayed: "mount.mvfs: Warning: unable to open mount table".

Fix: The ClearCase VOB mount code has been updated so that the system mount table is updated correctly on versions of Linux where it is virtual, rather than a file /etc/mtab.  With this fix, the warning message is eliminated.

Problem: After raising a VOB family to Feature Level 8, the ClearCase view_server logs show a warning on chmaster/protect events for new UCM types: "Unexpected vob event on vobserver."

Fix: The view_server will no longer log warnings for these events for the new UCM types.

14 Sept 2016

Superseded

Problem: In rare cases when automatically re-establishing a login session to an IBM Rational ClearCase CCRC WAN Server, a CTE, CMAPI or rcleartool client might consume all the sessions available on a CCRC WAN Server.

Fix: When automatically re-establishing a login session, a CTE, CMAPI or rcleartool client no longer consumes all the sessions available on a CCRC WAN Server.

Problem: The lockmgr documentation for ClearCase 8.0.1 and greater is incorrect.

Fix: The reference page for the lockmgr command has been substantially revised.

Problem: A long lived credmap_server process on an IBM Rational ClearCase will slowly consume additional process memory and will eventually crash.

Fix: The credmap_server memory leak has been fixed.

Problem: IBM Rational ClearCase Explorer may become unresponsive if the server authentication expires and the user has the preferences set to store and reuse the login credentials.

Fix: Fixes a problem in Rational ClearCase Explorer where it might previously become unresponsive if the server authentication expired and the user had the preferences set to store and reuse the login credentials.

Problem: When using IBM Rational ClearCase Explorer as an Eclipse plug-in, running in an Eclipse shell executing on an Oracle Java runtime environment, version 6, CTE fails to connect to the CCRC WAN Server with an error: CRMAP7009: Command "login" failed: Java.lang.Illegal StateException: null"

Fix: ClearCase Explorer running with the Oracle Java Runtime, version 6 now correctly connects to a CCRC WAN Server.

Problem: If the ClearQuest Web session time-out is set to a higher value than the license time-out, licenses for inactive CQ Web sessions are only released when the CQ session time-out occurs and not after the (earlier) license time-out. This could cause CQ Web users to consume too many licenses during busy times of the day.

Fix: Rational Common Licensing has been fixed so that inactive CQ Web sessions licenses are now released correctly according to the license time-out value as opposed to the higher web session time-out value.

Problem: The UCM/CQ integration was erroneously preventing deliver and other operations that involve CQ hooks from being performed in a CQ Web environment. An error would appear stating to use the "ClearQuest OSLC REST interface with ClearCase" even when that interface was already in use.

Fix: The UCM/CQ integration now allows deliver and other operations that involve CQ hooks to be performed in a CQ Web environment.

Problem: When working with the ClearCase Explorer integrated with RDz, the CLEARCASE_COMMENT variable entry is empty when the user adds an element of a logical model to source control.

Fix: Fixes a problem in ClearCase Explorer integrated with RDz to ensure that the CLEARCASE_COMMENT variable is properly set when the user adds an element of a logical model to source control.

Problem: If the ClearCase MVFS logging severity level is increased to "stale" on a Solaris 10 or 11 system running IBM Rational ClearCase, the occurrence of an NFS ESTALE error which triggers a logging event may cause a system panic.

Fix: A logging format error has been corrected, eliminating the chance for a null pointer reference.

Problem: In rare circumstances, when using an IBM ClearCase VOB with ACLs enabled, a heavily loaded view server process may crash due to invalid references to memory that has been reused.

Fix: view_server has been fixed to use properly allocated ACL data at all times.

Problem: When you are working in an IBM Rational ClearCase dynamic view, you may experience a Microsoft STOP error (blue screen crash).

Fix: IBM Rational ClearCase has been updated to fix a defect which caused an incorrect data to be accessed.

Problem: IBM Rational ClearCase rcleartool was assuming that a JSESSIONID would always be available to save with cached session data.

Fix: IBM Rational ClearCase rcleartool now checks that JSESSIONID is present before storing the current settings and writes the default value if it is not.

Problem: The ClearCase V9.0 knowledge center contained information about WebSphere that is applicable to ClearCase V8.0.x

Fix: The information has been updated to apply to ClearCase V9.0

Problem: When using the ClearCase Explorer Extension with RDz, you may find that the perference to decorate project names with view tags does not always work.

Fix: When using the ClearCase Explorer Extension with RDz the project names are now always decorated with view tags if the appropriate preference is set.

Problem: When working in an IBM Rational ClearCase dynamic view, you may experience a Microsoft STOP error (blue screen crash).

Fix: IBM Rational ClearCase has been updated to fix a defect which caused incorrect data to be accessed.

Problem: When using IBM Rational ClearTeam Explorer (CTE), there is a refreshing error when performing checkout or checkin of a file element if there is another checked out element that has been removed from the web view copyarea path.

Fix: The property that provides this information now skips files that cannot be found

Problem: Users of ClearCase dynamic views on MicroSoft Windows 10 may experience a Windows STOP error (blue screen), with bugcheck code "MULTIPLE_IRP_COMPLETE_REQUESTS"(44)"

Fix: The problem with incorrect IRP completion during I/O operations in ClearCase dynamic views on Microsoft Windows 10 is fixed by a Windows patch which is available in the patch rollup https://support.microsoft.com/en-us/kb/3176493

Problem: IBM ClearCase cleartool manpages for ACL administration commands (mkrolemap, chrolemap, lsrolemap, rmrolemap, mkpolicy, chpolicy, lspolicy and rmpolicy) are unable.

Fix: The cleartool man command displays manpages for ACL administration commands.

Problem: IBM Rational ClearCase automatic views mounted VOB tags (on a per-view basis) were handled in a case sensitive manner on Windows regardless of the setting of the MVFS case insensitive flag.

Fix: The MVFS case insensitive flag is now used when handling mounted VOB tags in automatic views on Windows.

Problem: In IBM Rational ClearCase ClearTeamExplorer (CTE) sub-directories of the VOBs are not shown in the "Apply Label" wizard GUI

Fix: Sub-directories of the VOBs will now be listed in "Apply Label" wizard and available for selection.

Problem: If an IBM ClearCase "rmstream" operation fails in the process of removing the foundation baselines from the configuration of the stream, then the STREAM record in the VOB is left in a corrupted state.

Fix: After the failure, some internal objects are deleted but the pointers are kept in the stream record. This fix checks internal objects existence before trying to delete it again on the next rmstream command.

Problem: IBM ClearCase rcleartool error handling failed to increment the argument counter for failed checkins, causing subsequent messages to be off my one.

Fix: Error handling has been corrected so that output element names are now synched with actual behaviour.

Problem: A locked IBM ClearCase pvob can cause "rebase -comp" to fail.

Fix: A new routine is used to remove broken hyperlinks caused by locked pvob, so "rebase-comp" can continue to create a new hype

Problem: In the IBM Rational ClearCase Cadence Integration, MultiSite SRFM operations do not show enough information for failures arising from checkouts at the remote sibling.

Fix: This fix improves the error message in the case where a checkout at a remote sibling blocks fulfillment of a SRFM operation.

Problem: IBM Rational ClearCase Windows dynamic views in case sensitve mode, case preserving mode was not respected. Names were always entered in lower-case.

Fix: On Windows, in case sensitive mode (not the common default which is case insensitive) the case preserving flag is now set correctly so names keep the case they were entered with.

27 May 2016

Superseded

Problem: Performing a checkout using a dynamic view in IBM Rational ClearCase ClearTeam Explorer (CTE) with a configuration specification (config spec) which selects a version other than LATEST on the branch results in a checkout of LATEST on that branch. Although a setting exists to allow web views to checkout the view selected version (Window > Preferences > IBM Rational ClearTeam Explorer > Dialogs > Checkout > "Checkout the version that is loaded even if it is not the latest", this setting does not change the behavior of dynamic views.

Fix: When performing a checkout in a dynamic view and the view-selected version is not the latest on the branch, the user is now allowed to choose whether to checkout the view-selected version or the latest version on the branch. A new set of preferences have been added for dynamic views: Window > Preferences > IBM Rational ClearTeam Explorer > Dialogs > Checkout >"Checkout the view-selected version even if it is not the latest on the branch" and "Checkout the latest version on the branch".

Problem: When working in Rational Developer for Z Systems with ClearTeam Explorer extension, you may find that the preference to decorate project names with view tags does not work in the HLL view.

Fix: When working in Rational Developer for Z Systems with ClearTeam Explorer extension, the preference to decorate project names with view tags now works correctly in all RDz views, including in the HLL view.

Problem: When working in Rational Developer for Z Systems with ClearTeam Explorer extension, you may find that the Team menu options are not correctly enabled in the HLL view.

Fix: When working in Rational Developer for Z Systems with ClearTeam Explorer extension, the Team menu options are now enabled correctly in the HLL view.

Problem: IBM ClearCase cleartool commands using "-fmt %[dstreams]Xp" may overflow its output buffer.

Fix: The "-fmt %[dstreams]Xp" option has been modified to expand its output buffer as needed.

Problem: When an Automatic view database attempts to reformat via the view db_dumper and db_loader, this can fail.  This leaves the view in an unusable state.

Fix: Automatic view reformat has been fixed.

Problem: When working in an IBM Rational ClearCase dynamic view, you may receive a Microsoft STOP error of BAD_POOL_HEADER (19).

Fix: IBM Rational Clearcase was changed to avoid this crash.

Problem: IBM Rational ClearCase cleartool command could crash if an excessively long string is passed as the -type argument

Fix: cleartool has been fixed to work properly with any length input string for the -type argument

Problem: When working in an IBM Rational ClearCase dynamic view and running the gnuwin32 cp.exe command, you may find that the file is not truncated correctly.

Fix: MVFS now notifies cache manager appropriately when changing the file allocation information removing the race condition.

Problem: Running the IBM Rational ClearCase command: "cleartool chmaster" on a read-only stream may result in an internal error.

Fix: The internal error is no longer reported.

Problem: After upgrade to update 3 of Solaris 11, starting IBM Rational ClearCase in any non-global zone on that system will cause a system crash.

Fix: The MVFS initialization code has been updated to work correctly on Solaris 11 update 3.

Problem: In some cases IBM Rational ClearCase users would find that they could not access views and vobs exported using non-ClearCase access and would receive STALE NFS FILE HANDLE errors.

Fix: STALE NFS FILE HANDLE errors when accessing views and VOB exported using non-ClearCase access have been resolved.

Problem: When using a tool such as kdiff to compare file differences between versions in two different ClearCase dynamic views on Microsoft Windows, the user may experience a Microsoft STOP error DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)

Fix: IBM Rational ClearCase has been updated to fix a defect which caused I/O data structures to be incorrect.

Problem: IBM Rational ClearCase "cleartool merge" or "cleartool diff" with the flags "-tiny" or "-window" on Linux may fail.

Fix: The xterm path location on Linux is correctly used.

Problem: When working in a ClearCase dynamic view in Microsoft Visual Studio, users may experience a Microsoft STOP error of BAD_POOL_HEADER (19) when opening a large project.

Fix: IBM Rational ClearCase has been updated to fix a defect which caused I/O data structures to be corrupted.

Problem: When performing a highly parallel build in an IBM ClearCase dynamic view, you may experience a system hang.

Fix: IBM Rational ClearCase MVFS was modified to avoid synchronization issues that was causing a system hang.

Problem: In IBM Rational ClearTeam Explorer the compare baselines OK button is grayed out and cannot be selected.

Fix: The OK button can now be selected.

Problem: When describing a file element version in an IBM Rational Clearcase Versioned Object Base (VOB), the output will be truncated at 153097 bytes when formatting the describe to only return labels. (-fmt %Nl)

Fix: The output buffer used by -fmt %Nl now expands as needed to include all labels.

Problem: When using Microsoft Visual Studio and searching within a large project in an IBM ClearCase dynamic view, you may experience a Windows STOP error (BSOD) when opening a file found during the search.

Fix: IBM Rational ClearCase has been updated to fix a defect which caused I/O data structures to be incorrect.

Problem: When performing a highly parallel build in an IBM ClearCase dynamic view, you may experience a Microsoft Windows STOP error (blue screen crash) with the status  DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1).

Fix: IBM Rational ClearCase has been updated to fix a defect which caused I/O data structures to be incorrect.

Problem: In IBM Rational ClearCase, when creating an integration view from the "join project" dialogue in ClearTeam Explorer, the "Finish" button is greyed out.

Fix: In the problem case, the "Finish" button can now be selected.

Problem: When performing container recovery/repair in an IBM Rational ClearCase Versioned Object Base (VOB) the checkvob command may fail while processing damaged UTF16 or UTF32 elements.

Fix: The checkvob command is now able to process UTF16 and UTF32 elements.

Problem: When attempting to repair missing/corrupt source containers in an IBM Rational ClearCase Versioned Object Base (VOB), the checkvob tool may incorrectly determine the storage format of the potential replacement container when the element type manager is one of the more-recently introduced element types: Rose/xde/Unicode, etc.

Fix: The correct element type is now detected and used.

Problem: IBM ClearCase cleartool commands using "-fmt %[CONFIG_SPEC]P" may overflow its output buffer.

Fix: The "-fmt %[CONFIG_SPEC]P" option has been modified to expand its output buffer as needed.

Problem: When you are running the following command against an IBM Rational ClearCase Access Control List (ACLS) enabled vob, you may receive an error: cleartool lspolicy policy:PolicyName@\VOB tag cleartool: Error: Policy not found: "policy:PolicyName".

Fix: Both formats of the lspolicy command (""  "policy:") are now accepted.

Problem: IBM ClearCase clearmake on a unix platform may crash with a segmentation fault for a specific clearmake case where a target has multiple dependencies, and in the building of the target, one or more of the dependencies are specifically removed.

Fix: Clearmake has been updated to properly handle this specific case.

Problem: Incorrect user is identified as checking in a file in ClearTeam Explorer if a merge is required due to a previous checkin.

Fix: The correct owner will be now be reported in the message.

Problem: When IBM ClearCase clearmake is executed with the environment variable MAKEFLAGS set to a name/value pair of a specific length, clearmake may crash with a segment fault.

Fix: Clearmake has been modified to not crash under the specific name/value pair length situation.

Problem: When attempting to checkin a large directory/element set with the aggregated checkin function, the operation will appear to hang and never complete.

Fix: List of checkouts is now only fetched once when get aliases.

Problem: When working in an IBM Rational ClearCase UCM Multisite environment having mutiple pvobs, it is possible that oplogs generated by running "cleartool rebase -dbaseline" may not be replayed properly in sibling replicas, causing subsequent failures at those siblings when running "mkreplica -export" or "reformatvob" commands.

Fix: This fix causes the oplogs to be replayed properly at sibling replicas.

Problem: A ClearCase Windows client using a Unix/Linux view to access an ACL enabled VOB may get access denied even though the client's primary group matches the owner group of the VOB.  One manifestation could be a "dir /acl-enabled-vob-name" command would show no contents in the VOB with no other apparent error.

Fix: ClearCase was modified to check the primary group as well as the grouplist when looking for a matching group during ACL checks.

17Mar2016

Superseded

Problem: UCM MULTISITE: REBASE INFORMATION NOT PROPAGATED TO SIBLING REPLICAS

Fix: New oplog is created to propagate "sideway" rebase operation to sibling replicas. 

Problem: When performing an rcleartool diff vs predecessor, the predecessor version was being fetched without taking the view text mode into consideration. This could cause all lines to show as different due to mis-matched line termination.

Fix: The underlying RPC which supports the fetch of non-loaded versions for rcleartool diff now supports communication of the view being used for the operation so that the server can use the correct text mode for constructing the cleartext.

Problem: When using the ClearTeam Explorer, the Pending Changes view does not show the changes incoming from a view update

Fix: Fixes a problem in the ClearTeam Explorer where the Pending Changes view does not show the changes incoming from a view update

Problem: When attempting to repair missing/corrupt source containers in an IBM Rational ClearCase Versioned Object Base (VOB), the checkvob tool may incorrectly determine the storage format of the potential replacement container when the element type manager is one of the more-recently introduced element types: Rose/xde/Unicode, etc.

Fix: The correct element type is now detected and used.

Problem: When performing container recovery/repair in an IBM Rational ClearCase Versioned Object Base (VOB) the checkvob command may fail while processing damaged UTF16 or UTF32 elements.

Fix: The checkvob command is now able to process UTF16 and UTF32 elements.

Problem: When using the IBM Rational ClearCase xcleardiff tool to merge files on Ubuntu 14.04, the following error occurs: /opt/rational/clearcase/lib/mgrs/text_file_delta/xmerge: symbol lookup error: /opt/rational/clearcase/lib/mgrs/text_file_delta/xmerge: undefined symbol: XmRedisplayWidget

Fix: The xcleardiff tool has been repaired so that it works correctly on Ubuntu 14.04

Problem: If you are working in an IBM Rational ClearCase dynamic view on Microsoft Windows, you may experience a  hang on operations accessing file objects in a view or VOB.

Fix: There is a scenario in which MVFS was trying to acquire a lock with no need that would lead to a dead lock. The lock acquisition was removed on that specific scenario.

Problem: On all UNIX platforms, performance of "ls -l" at the VOB mount point is very slow after some period of inactivity. Additionally, the performance of commands that issue a getcwd() library can be slow on some UNIX platforms if the getcwd() obtains metadata for all mounted VOBS at the VOB mount point.

Fix: As a performance optimization, the last vobrpc_server for a VOB will never exit for all UNIX platforms.

Problem: ClearCase MultiSite documentation does not explain that when the VOB family feature level of a replica is 8, changing a replica from non-preserving to preserving is blocked to prevent inconsistent notions of identities and permissions among members of the VOB family.

Fix: The following topic have been updated to address the omission: the overview of feature levels in MultiSite administration documentation, the reference pages for the multitool chreplica command, and the reference page for the cleartool chflevel command.