Fixes Defects:

PM01862,PM23142,PM34445,PM41812,PM49234,PM52447,PM55490,PM60069,PM60259,PM60302,PM60644,PM60858,PM62172,PM62396,PM62811,PM63804,PM64431,PM65573,PM67204,PM68891,PM69855,PM70055,PM70580,PM70793



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).


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.


PM64431:

   Problem: 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.


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.


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".


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.


PM69855:

   Problem: In an IBM HTTP Server (IHS) load balanced IBM Rational Change Management (CM) Server environment when multiple requests are in flight concurrently, only one request will have the JSESSIONID from a previous response.  Each request should use this same JSESSIONID.  Instead all other requests will use a JSESSIONID of null. This results in "expired session" error and a login to another server which in turn collapses the IBM Rational ClearCase Remote Client (CCRC) navigator tree.

   Fix: Multiple concurrent requests from the same instance of the CCRC client will share JSESSIONIDs correctly.


PM70055:

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

   Fix: ARRAY(0x95583c8)


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.