Fixes Defects: PI15110,PI40960,PI43668,PI45746,PI45760,PI50577,PI50990,PI52979,PI53844,PI55768,PI57453,PI57857,PI58916,PI59905 This patch contains the following software changes: PI15110: 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. PI40960: 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. PI43668: Problem: IBM ClearCase cleartool commands using "-fmt %[CONFIG_SPEC]P" may overflow it's output buffer. Fix: The "-fmt %[CONFIG_SPEC]P" option has been modified to expand it's output buffer as needed. PI45746: 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. PI45760: 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. PI50577: 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. PI50990: 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. PI52979: 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. PI53844: 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. PI55768: 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. PI57453: 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. PI57857: 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 PI58916: 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. PI59905: Problem: IBM ClearCase cleartool commands using "-fmt %[dstreams]Xp" may overflow it's output buffer. Fix: The "-fmt %[dstreams]Xp" option has been modified to expand it's output buffer as needed.