Fixes Defects:

PI28582,PI41700,PI44831,PI68851,PI69005,PI72644,PI73132,PI73135,PI73356,PI73587,PI73735,PI73751,PI74251



This patch contains the following software changes:


PI28582:

   Problem: In a ClearCase nonpreserving replica with ACLs enabled, syncreplica replay of a mkelem oplog may generate a second "create file element" event in the database, which can cause failures in reformatvob and mkreplica -import.

   Fix: The duplicate "create" event will no longer be generated.


PI41700:

   Problem: ClearCase chtype may fail in windows client / server configuration due to missing cleartext; the cleartext is generated but there is a delay of ~ 5 seconds before the client sees the cleartext file (due to Windows SMB2 caching).

   Fix: The chtype command has been fixed to fail without committing any changes when a version's cleartext is unavailable.  
These Windows  registry keys can be set to '0'  (all DWORD) to disable the portion of Windows SMB2 caching causing the problem.
 
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Lanmanworkstation \Parameters 
DirectoryCacheLifetime=0 
FileNotFoundCacheLifetime=0 
FileInfoCacheLifetime=0


PI44831:

   Problem: When using CtCmd with Rational ClearCase "cleartool describe -fmt" the output is truncated by one byte if the first string is 16384 characters and the second the second string is one byte longer than the first.

   Fix: Cleartool describe buffer handling was fixed.


PI68851:

   Problem: When using the ClearCase Remote Client command line interface -- rcleartool -- attempts to use rcleartool mkattr to create or update a string attribute may fail with 'invalid string "{passed string}"'.

   Fix: Non-interactive invocations of rcleartool mkattr for string attributes no longer strips the embedded quotes and should apply the attribute properly.


PI69005:

   Problem: The ClearCase binary_delta  type manager may not remove temporary file(s) after a failed type manager operation.

   Fix: The ClearCase binary_delta  type manager was fixed to remove temporary files.


PI72644:

   Problem: In rare situations, ClearCase clearmake could hang when starting a child process to execute a build step.

   Fix: ClearCase clearmake has been fixed to continue execution properly when starting child processes.


PI73132:

   Problem: On AIX 7.1, using the open() system call with the O_CLOEXEC flag to open a file/dir in the ClearCase MVFS returns EINVAL.

   Fix: On AIX 7.1 (and later) the O_CLOEXEC flag can now be used to open a file/dir in the ClearCase MVFS.


PI73135:

   Problem: ClearCase users may see intermittent Access Denied errors when accessing files using non-ClearCase Access if the VOB root directory does not have execute permissions set.

   Fix: Capability checks have been added to the MVFS permission checks to resolve this situation.


PI73356:

   Problem: ClearCase "chmaster -stream" may not change mastership of timeline objects.

   Fix: On schema 80 and feature level 8, "chmaster -stream" will change mastership of timeline objects whether it has timeline folder or not.


PI73587:

   Problem: When working in ClearTeam Explorer (CTE) , you may find that the file you just checked out does not appear to be checked out only when the path is accessed through address bar.

   Fix: Check out status is displayed as expected in ClearTeam Details pane, even when the file is accessed from the address bar.


PI73735:

   Problem: Users of ClearCase on Oracle Solaris 11 may experience a system crash when using NFS-mounted remote VOB storage.

   Fix: A defect in the ClearCase MVFS, which caused corruption of NFS data, has been fixed.


PI73751:

   Problem: Some xattr operations on ClearCase view or VOB files on SUSE Linux may cause D-STATE (zombies) processes.

   Fix: ClearCase MVFS was changed to avoid acquiring the inode mutex for xattr operations.


PI74251:

   Problem: File lock operations on ClearCase files when the view storage is NFS4 may result in error EBADF (Bad file number).

   Fix: The Linux MVFS driver was modified to set the file access mode that can be accepted by NFS4.