Fixes Defects:

CS0151797,CS0266062,CS0303560,PH36404,PH38407,PH42350,PH44551,PH44670,PH44742,PH45164,PH46541,PH46918,PH47569,PI72597,PI79611



This patch contains the following software changes:


CS0151797:

   Problem: When running ClearCase clearmake in a parallel, or distributed, mode, may 'hang' if there is an issue with starting up an abe process.  If an abe has been started, and clearmake has assigned a target to that abe, and then the abe fails to start up in time, or there is a communication problem between clearmake and the abe, clearmake will try and assign the target to a different abe, and clearmake may hang if there are any problems trying to re-assign that target to a different abe.

   Fix: The ClearCase clearmake code has been updated to properly handle the situation where there is a communication issue between clearmake and an abe.   clearmake will either properly re-assign the target to another abe, or clearmake will indicated that the building of that specific target has failed.


CS0266062:

   Problem: Poor signal handling can result in a race condition when forking new processes, causes thread deadlock and ClearCase albd hang.

   Fix: ClearCase now better manages signals during process startup.


CS0303560:

   Problem: ClearCase "cleartool getcache -view -cview"  may show negative values.

   Fix: ClearCase "cleartool getcache -view -cview"  output format(s) were corrected.


PH36404:

   Problem: On a ClearCase Multisite recursive import failure, the condition check before deleting a packet was missing to check if there is any target VOB available or not. It was only checking the variable which updates when -invob is provided. Hence, import process assumed there were no target VOB available and packet was deleted. 
 

 

   Fix: Added an additional check to verify target VOBs for recursive import.


PH38407:

   Problem: The ClearCase startup script may fail to create /var/lock/subsys.

   Fix: The logic of the ClearCase startup script (creation of /var/lock/subsys) was improved.


PH42350:

   Problem: When creating a new view using the ClearCase front desk, the "Edit view configuration" window appears and then "disappears." 

A quick look at the active windows on a host shows that the window is still present, but has been moved to the background and has thankfully lost focus.


   Fix: When creating a new view using the ClearCase front desk, the "Edit view configuration" window pop-up and appear.
And there is no focus loss issue after the fix.


PH44551:

   Problem: ClearCase triggers that prompt for user input fail.

   Fix: ClearCase trigger control flags have been fixed.


PH44670:

   Problem: Non-ClearCase mounts (nca exported view/VOB) may not resolve symlinks on Linux with kernel after 3.13 inclusive.

   Fix: The ClearCase MVFS was fixed to work correctly with Linux kernel 3.13 and superior.


PH44742:

   Problem: When installing ClearCase 9.0.1.x, 9.0.2.x, and 9.1.0.x on a Linux host using IM 1.9 or later, the /etc/updatedb.conf file is edited incorrectly, preventing the database for the "locate" command from being updated. 


   Fix: Processing of the /etc/updatedb.conf file has been fixed.


PH45164:

   Problem: The ClearCase checkvob operation may incorrectly report elements as being locked.

   Fix: Fix allows the ClearCase checkvob operation to proceed correctly.


PH46541:

   Problem: ClearCase clearmake may crash when exiting.

   Fix: ClearCase clearmake shutdown/exit has been improved.


PH46918:

   Problem: Mounting ClearCase automatic views on Linux may cause a kernel crash.

   Fix: The mount parameters treatment was modified to avoid the crash.


PH47569:

   Problem: When importing sync packets, VersionVault MultiSite fails without printing an error message if EOF of a packet file is reached while fetching version data or the follow-on packet is missing or this was the only packet in the set.

   Fix:  For better understanding we are adding a error message which will print on console in this case.


PI72597:

   Problem: While creating a ClearCase brtype with "-global -acquire" flags, it internally acquiring ordinary types of same name even though object mastership is not present. So it leads to creation of multiple global definition hyperlinks for local type.


   Fix: Restricting the creation of brtype with "-global -acquire" if mastership of acquired brtype is not in the referenced component vob. 
So that it will prevent multiple global definition hyperlink creation on brtype with same name


PI79611:

   Problem: In the Rational ClearTem Explorer (CTE)  ClearQuest (CQ) client,
you may find that the static text fields populated by another
field (via field dependency) show up blank, rather than the
expected value. When the user Click on the "Customer" tab, find the field "new_field" and populate it with a value and the same value should be reflected in the static text field.
      However, the refresh doesn't happen and the static text field just shows the label.
    

   Fix: When the user clicks on the "Customer" tab, find the field "new_field" and populate it with a value and the same value reflected in the static text field.