Fixes Defects:

PM01862,PM23142,PM34445,PM41812,PM49234,PM52447,PM55490,PM60069,PM60259,PM60302,PM60644,PM60858,PM62172,PM62396,PM62811,PM62894,PM63804,PM64329,PM64431,PM64899,PM65457,PM65573,PM65832,PM65952,PM65979,PM6598,PM66323,PM66577,PM66596,PM66796,PM66857,PM66878,PM66879,PM66880,PM67191,PM67204,PM67670,PM67890,PM68415,PM68416,PM68431,PM68891,PM70037,PM70055,PM70580,PM70793,PM71611,PM71680,PM71693



This patch contains the following software changes:


PM01862:

   Problem: Corrects a Clearcase MVFS problem where MVFS incorrectly handled the read-only flag of the files.

   Fix: The way that MVFS handles read-only files on Windows was changed.


PM23142:

   Problem: The cleartool 'ls' command will occasionally report an error, "cleartool: Error: Trouble reading directory", when issued within a directory under the control of the ClearCase MVFS.

   Fix: ClearCase's caching and synchronization logic was modified to more quickly detect and adapt to remote changes of directory versions.


PM34445:

   Problem: db_server unnecessarily calls sysutl_nfs_flush twice for each read transaction

   Fix: A fix is available in ClearCase versions 7.1.2.8 and 8.0.0.4


PM41812:

   Problem: Windows VOB servers may time out attempting to lock the vista.taf file.

   Fix: Allow the ability to modify the delays between lock attempts, and the number of attempts before aborting the lock attempt.


PM49234:

   Problem: Under consistent heavy load on a given ClearCase dynamic view client, "xid mismatch" errors are encountered in MVFS and is logged accordingly in mvfs_log.

   Fix: Fixes a problem in ClearCase and resolves the "xid mismatch" error.


PM52447:

   Problem: In UCM if the user has created baselines on a stream and rebases to a composite baseline which is the original foundation baseline of the stream or in other words at the '0'th index of the timeline for that component , then lsbl -component will not display the baseline created by stream on the master site and will give INTERNAL ERROR on the other replica sites.

   Fix: The lsbl -component display now shows the UCM baseline properly at the replica sites.


PM55490:

   Problem: customer may have VOB access issue at the time when an element with a large number of branches and/or versions.  

   Fix: a clear warning message with good info is provided and customer is encouraged to manually remove some branches/versions before finally destroying the element to avoid VOB access issue.


PM60069:

   Problem: crmregister -gui option does not work with the -url option when user credentials are not specified on the command line.

   Fix: crmregister correctly supports the prompting for user credentials when -url and -gui options are used together.


PM60259:

   Problem: Wildcard registry lookups don't scale for registries with a large number of objects

   Fix: A fix is available in ClearCase versions 7.1.2.8 and 8.0.0.4


PM60302:

   Problem: Occasionally, system facilities such as the 'pwd' command and the 'getcwd' function and its equivalents will fail when executed from within a newly created directory under control of the ClearCase MVFS.

   Fix: The ClearCase MVFS's cache and synchronization logic has been corrected to prevent the caching of invalid directory entry information during periods of heavy load.


PM60644:

   Problem: When using IBM Rational ClearCase's makefile based build utility Clearmake, it throws "clearmake: Error: Unable to place marker in MVFS audit - Invalid argument" error for the recursive builds where parent make is invoked with .NO_CONFIG_REC target and there is no fresh build happening in the child make.  This behaviour is seen in  ClearCase 7.1.2.7 or 8.0.0.3 or prior versions.

   Fix: After the fix, for the recursive make builds where parent build audit is not getting audited and there is no fresh build happening in the child make, the error "clearmake: Error: Unable to place marker in MVFS audit - Invalid argument" will not be thrown.


PM60858:

   Problem: ClearCase Project Explorer crashes when obtaining Policies of a CQ-enabled UCM project with certain schemas.

   Fix: Resolves an issue in the UCM ClearCase integration with ClearQuest where certain UCM schemas would cause the ClearCase Project Explorer to crash when obtaining CQ Policies.


PM62172:

   Problem: When using IBM Rational ClearCase and Microsoft Windows Explorer integration on a Windows 64-bit machine running ClearCase 7.1.2.6 or 8.0.0.2, few of the applications selected in the ClearCase context menu appeared in the background, rather than in the foreground.

   Fix: After the fix, the applications or dialogs invoked from ClearCase context menu available in Windows Explorer will appear in the foreground.


PM62396:

   Problem: When running in an interactive cleartool shell, after executing a cleartool command that modifies ClearCase environment variables, and then executing a shell command (!), there are some ClearCase environment variables that remain set in the new shell environment, which may affect future Cleartool commands.

   Fix: When executing a shell command (!) while in an interactive cleartool command, the ClearCase environment variables are cleared.


PM62811:

   Problem: The Base ClearCase-ClearQuest V2 integration will not permit a file or directory to be checked-in when the checkin comment is too long.

   Fix: Long comments are truncated to appropriate length according to Windows XP and Windows 2003's limitation on the total length of environment variables (EVs).


PM62894:

   Problem: ClearCase operations such as checkout of UTF8 type files fails with CCRC WAN Server crash. 

   Fix: UTF8 type files are now checked out successfully without a CCRC WAN Server crash


PM63804:

   Problem: Lock obsolete a foundation baseline of a child stream results in all baselines on that stream not being displayed in the base. If a component baseline that happens to be also a foundation baseline of a stream is locked-obsolete, then the component tree browser with the "Show obsolete baselines" tick-box unset, hides not only that baseline, but also and incorrectly *all* the baselines of the stream of which the just locked-obsoleted baseline is the foundation baseline.

   Fix: The fix ensures that If you have an obsolete baseline which is the foundation baseline for other stream, after unselecting the option for "Show obsolete baselines", the display should only hide the obsolete baseline and not any other nodes (other streams and non-obsolete baselines). 
If any node is made invisible, the connection line is drawn between its adjacent visible nodes.


PM64329:

   Problem: A large number of such failed CCRC login attempts in a short period of time may cause CCRC WAN Server to reach the ccrcMaxSessionsOverall limit (200 by default), preventing other legitimate users from logging in.

   Fix: Failed logins are no longer counted against the max sessions overall limit, which keeps the server sessions free for normal use.


PM64431:

   Problem: ClearCase Mainframe Connectors (CCz) takes some of Chinese characters in comments as invalid.

   Fix: A fix is available in 7.1.2.8 and 8.0.0.4.


PM64899:

   Problem: Some operations with webviews in IBM Rational ClearTeam Explorer 8.0 may be slower than IBM Rational ClearCase Remote Client (CCRC).  Examples include mkelem and checkin.

   Fix: A fix for the performance issue is available in Rational ClearCase release 8.0.0.4.


PM65457:

   Problem: SUMMARY:
Documentation of how the CLEARCASE_MKELEM_USE_GRPLIST environment variable functions, common code, for two different commands is different.  Specifically, the documentation for under the 'mkdir' command is simply wrong and should duplicate the correct information as documented under the 'mkelem' command.

>>> Infocenter (7.1 + 7.1.2 + 8.0) mkdir <<<

   1. If the process primary group is among the VOB groups, then that group becomes the new element's group; else mkelem determines whether the VOB group is among the process groups.
    2. If the VOB group is among the process groups, then that group becomes the new element's group; else mkelem takes the intersection of the VOB groups and process groups.
    3. If the intersection yields exactly one group, then that group becomes the new element's group.
   4. If the intersection is not unique or is empty, then an attempt is made to use the process primary group; in this case, element creation will fail.

>>> Infocenter (7.1 + 7.1.2 + 8.0) mkelem <<<

    1. If the process primary group matches any VOB group, then that group becomes the new element's group; else
   2. If the intersection of all process groups and all VOB groups yields exactly one group, then that group becomes the new element's group; else
    3. Element creation fails.

   Fix: Fixed as directed.


PM65573:

   Problem: UCM GUIs (such as clearprojexp.exe) issue multiply redundant identical RPCs to the db_server, thus reducing overall performance.

   Fix: The number of RPCs sent from the client to the server has been reduced due to a more intelligent caching scheme as well as a rework of some of the RPCs used in retrieving information about ClearCase objects.


PM65832:

   Problem: Login to CCRC WAN server (Rational ClearCase v 8) fails with the following error when the name of the host where CCRC WAN server is installed starts with the characters "ccrc" (e.g. ccrc-test or ccrctest).

CRMAP7009: CCRC command "Login" failed: Error:"Malformed server response.
The server at "http://ccrc" is not a correctly configured ClearCase Web Server."

   Fix: The CCRC client code has been modified to correctly handle CCRC WAN Server URLs which have the characters "ccrc" in their host name


PM65952:

   Problem: Incorrect encoding was being used on the message.properties file for German

   Fix: File has been changed to use the appropriate encoding


PM65979:

   Problem: When a new file element is added to a VOB using the command line(cleartool mklem) that was first added as view private file using IBM Rational ClearTeam Explorer (CTE) most of the file element context menu options such as checkout etc  are greyed out in the right click menu even after refresh(from context menu) is done on the file element. After CTE is restarted the menu options are available in the right click context menu.

   Fix: The IBM Rational Clear Team Explorer code has been modified to re-fetch the relevant property of the file element when the user selects the refresh option from the right click context menu options


PM6598:

   Problem: In the reference page for the rmstgloc command, the "Description" section of page contradicts information in the "Restrictions" section.

   Fix: The Description section of rmstgloc has been updated as follows:

" ...  Once a storage location is unregistered, you cannot create views or VOBs using mkview –stgloc or mkvob –stgloc. However, you can create views and VOBs at that storage location using the –host, –hpath and –gpath options. ... " The Restrictions section has been updated to note that there are no restrictions.


PM66323:

   Problem: The ClearTeam Explorer performs poorly when using large model projects

   Fix: Fixes a performance problem in the ClearTeam Explorer that hindered logical model usage.


PM66577:

   Problem:  Directory merge not working in CTE

   Fix: Fixes a problem with ClearCase where CTE fails to automatically merge the project directory following a Logical Model Merge.


PM66596:

   Problem: Closing the Logical Model Merge Editor via the 'Close' or 'X' button, will lose the merge result

   Fix: Fixes a problem in ClearCase where closing the Logical Model Merge Editor via the "Close" or "X" button will lose the merge result.


PM66796:

   Problem: The ClearTeam Explorer versoin tree truncates the label name by default, thus not allowing a user to see the full name. This is problematic when the most significant characters are at the end of the string.

   Fix: The ClearTeam Explorer provides a button that allows a user to toggle between truncated names and full names. The last state of the button is persisted for the workspace or until changed.


PM66857:

   Problem: In the reference page for the clearfsimport command, the descriptions of the -filter and -mklabel options are incorrect.

   Fix: The descriptions have been updated as follows:

–filter
Determines which elements need to be checked out for the import to succeed and checks out only those elements. When this option is specified with –mklabel , the label is applied to newly created directory versions only.

–mklabel label
Attaches the specified label instance to each element that matches the name of an imported file or directory, whether or not a new version is created. If the label type does not exist, it is created. If the label is already attached to an existing element version, it is moved.


PM66878:

   Problem: Remotely added model elements become view private after merge in target view

   Fix: Fixes a problem in ClearCase where remotely added model elements become view private in the target view after Logical Model Merge.


PM66879:

   Problem: When model aware checkouts are enabled in the ClearTeam Explorer, the checkout dialog opens with all elements participating in the logical resource selected for checkout. Customer requires that only those elements selected by the user are selected by default.

   Fix: The ClearTeam Explorer provides a new preference that enables the checkout dialog to open with all logical resource elements selected or only those logical resource elements selected by the user.


PM66880:

   Problem: The ClearTeam Explorer version tree  does not allow the ability to sort labels in the order in which they were applied with the most recent displayed first.

   Fix: The ClearTeam Explorer version tree provides a button that allows a user to toggle between label names sorted alphanumerically and label names sorted by the time they were applied (most recent first). The last state of the button is persisted for the workspace or until changed.


PM67191:

   Problem: Aggregated checkin not showing dialog with checked-out files in views with checkouts in non-mounted VOBs.

   Fix: The server no longer returns checkouts in umounted VOBs to clients, which allows the dialog to display without issue.


PM67204:

   Problem: During an audited build, MVFS must write to the audit file, along with whatever other file activity that is triggered by the build itself. Sometimes the audit file was being updated while omake was trying to stop the audit, so the file system returns an error and the "unable to stop MVFS audit" was shown.

   Fix: The resolution corrects the error "unable to stop MVFS audit".


PM67670:

   Problem: The ClearTeam Explorer does not provide any means to copy a label name as text from the Version Tree.

   Fix: The ClearTeam Explorer now provides the user the ability to select a label name from the version tree, right click and copy the label's name.


PM67890:

   Problem: CTE should show model checkouts in a model-friendly way and allow navigation from a checked out file to them model element in the Project Explorer.

   Fix: Support for this feature available in Rational ClearTeam Explorer v 8.0.0.4.


PM68415:

   Problem: Refactoring not working in the Modelling perspective

   Fix: Fixes a problem in CTE where refactoring was not working in the Modelling perspective because the Checkout dialog was inaccessible.


PM68416:

   Problem: Resource->Refresh does not work for logical resources in the Details view

   Fix: Fixes a problem in CTE where Resource->Refresh in the Details view does not work for logical resources


PM68431:

   Problem: Rational ClearCase ClearTeam Explorer does not show the size of both controlled and view private file elements in the ClearTeam details view in the size column

   Fix: The Rational ClearCase ClearTeam Explorer code has been modified to correctly display the size of controlled and view private file elements in the ClearTeam Details view


PM68891:

   Problem: When the local administrator creates a new scripts location in the IBM Rational Report Builder, the script location is visible. 
 The default script location is either C:\Program Files\IBM\RationalSDLC\ClearCase\reports\ or C:\Program Files (x86)\IBM\RationalSDLC\ClearCase\reports\.   

The local administrator can change the script to any location on the system, for example, C:\scripts.  This location is correctly entered in the Microsoft Windows Registry under either HKLM\Software\Atria\ClearCase\CurrentVersion or HKLM\Software\Wow6432Node\Atria\ClearCase\CurrentVersion. 
When the administrator checks the path in the Report Builder, the path is correct. 
 When a standard user logs on to the same machine that has just been modified and checks the path to the scripts, it points to the default path and not the new location. 

Since the value is set under HKLM, any user logging in to the machine should get the modified path.

   Fix: After the fix, newly created scripts location will be visible to all users.


PM70037:

   Problem: The ClearTeam Explorer throws a NullPointerException during decoration.

   Fix: Fixed a ClearTeam Explorer problem that can result in a NullPointerException during decoration


PM70055:

   Problem: During upgrades of IBM Rational ClearCase, some registry keys will be deleted and configurations will be reset to defaults.

   Fix: ARRAY(0x9581b44)


PM70580:

   Problem: When a rebase backward/sideways is done for a rootless component it causes the removal of a Foundation hyperlink.
  The Foundation hyperlink is always FROM a baseline TO the  "timeline".
  There is a reference to the hyperlink in the "Activity timeline" string of the timeline object,
    which gets removed when the timeline gets removed.

However, when the baseline and the timeline exist in different UCM project VOBs,
  then while an oplog entry is generated for both project VOBs, the processing to remove the entry from the "Activity timeline" string of the timeline object does not occur when the oplog entries are replayed.

   Fix: After the fix when a rebase backward/sideways is done , the existing Foundation hyperlink is not deleted.


PM70793:

   Problem: albd server crashes with double-free error when checking -user line in license file.

   Fix: Problem has been fixed and release on 2012C patch.


PM71611:

   Problem: When using dynamic views, the ClearTeam Explorer intermittently performs UI blocking operations in the IDE workspace, that causes the user to wait.

   Fix: Addresses an optimization issue in the ClearTeam Explorer and enables better performance when interacting with ClearCase.


PM71680:

   Problem: ClearCase MultiSite syncreplica imports fail between VOB servers running ClearCase 7.1.2.x and ClearCase 8.0.0.x for replicas in a Feature Level 6 VOB family, because of packet header mismatch in ClearCase 8.0.0.x.

   Fix: This change restores the ability to correctly generate and read syncreplica packets in Feature Level 6 replicas in ClearCase 8.0.0.x.


PM71693:

   Problem: The ClearTeam Explorer display contributors in the incorrect order why using Model compare

   Fix: Fixes an issue in the ClearTeam Explorer where compare contributors are not displayed in the correct order when using Model compare.