Fixes Defects: PI15110,PI31561,PI36172,PI40960,PI41762,PI43174,PI43668,PI45746,PI45760,PI48197,PI52979,PI53155,PI54375,PI56221,PI56714,PI57204,PI57857,PI59748,PI59905,PI60065,PI60070,PM79307 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. PI31561: 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. PI36172: 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. 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. PI41762: 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. PI43174: 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. 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. PI48197: 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. 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. PI53155: 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. PI54375: 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. PI56221: 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. PI56714: 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. PI57204: 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. 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 PI59748: 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. 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. PI60065: 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. PI60070: 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. PM79307: 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".