Error during ClearCase Stream Property Fetching

This technote identifies a defect where attempts to select the properties of a read only UCM stream using the Metadata Navigator in IBM® Rational® ClearCase® Remote Client (CCRC) version 7.0.1.CU02 results in an error stating, An error has occurred. See details for additional information, yet the dialogue box is empty.

Cause

Note: This only happens with "read-only" streams. Error During ClearCase Stream Property Fetching X  An error occurred. See details for additional information. This issue has been logged as defect APAR PK37277.

Solution

There is currently no solution for this issue. WORKAROUND: Use a Full ClearCase client to view the properties of a Read-Only Stream until this feature is corrected in CCRC.

ClearCase Remote Client fails to start after installation

This technote provides instructions on how to work around a defect related to the IBM® Rational® ClearCase® Remote Client package included in the latest 2003.06.00 UNIX® and Linux® patches released February 23, 2006.

Cause

Attempts to start the stand-alone version of CCRC installed from a UNIX or Linux host which was installed or upgraded from a release area with the below patches applied results in the following error: !MESSAGE Plug-in "com.ibm.rational.clearcase.standalone" was unable to instantiate class "com.ibm.rational.clearcase.standalone.plugin.StandaloneApplication". DIAGRAM: UNIX Release Area with affected patches ==> ClearCase install  ==> CCRC install from client or RWP server AFFECTED PATCHES ClearCase on UNIX clearcase_p2003.06.00-31 ClearCase on UNIX (International) clearcase_p2003.06.10-31 ClearCase LT on UNIX clearcase_lt_p2003.06.00-16 Note: Clients installed from a release area patched before the affected versions above will not experience any problems installing or updating CCRC. Symptoms include opening the CCRC client after installation producing an error that directs you to a log file which does not exist. Defect APAR IC48964 has been submitted to address this issue.

Solution

This defect has been resolved in the following updates ClearCase on UNIX clearcase_p2003.06.00-40 ClearCase on UNIX (International) clearcase_p2003.06.10-40 ClearCase LT on UNIX clearcase_lt_p2003.06.00-19 Note: Whether the CCRC installation was performed from the Rational Web Platform (RWP) server or from a client, the following steps need to be taken on ALL hosts that were installed or upgraded from a release area on UNIX applied with the above affect patches. WORKAROUND: 1. Uninstall CCRC on the affected clients. 2. Download both CCRC bits below and copy to the RWP server, clients or any hosts installed or upgraded from the UNIX release area with the affected patches: New CCRC bits have been released as of March 24, 2006. ClearCase on UNIX CCRC fix ClearCase on UNIX (International) CCRC fix ClearCase LT on UNIX CCRC fix 3. Overwrite the zip archive in the following location on the RWP server: Windows: C:\Program Files\Rational\ClearCase\web\update Linux/UNIX: /opt/rational/clearcase/web/update 4. Reinstall the CCRC client. RELEASE AREA WORKAROUND: The replacement files above cannot be added to the release area in order to alleviate future CCRC install problems. Note: If your primary method of CCRC installation is performed from the RWP server, the steps above should be sufficient to resolve all issues; however, if CCRC is installed from any other hosts that have been installed or upgraded from the UNIX release area with the affected patches, the following option is available. Restore the release area to its predecessor release. 1. Delete the release area with the latest patches applied. 2. Create a new release area using the following predecessor patches: ClearCase on UNIX clearcase_p2003.06.00-29 ClearCase on UNIX (International) clearcase_p2003.06.10-29 ClearCase LT on UNIX clearcase_lt_p2003.06.00-15

Unable to fetch delivery target stream

This technote identifies a defect where the IBM® Rational® ClearCase® Remote Client can not create views based on a read-only stream.

Cause

The following error occurs while attempting to create a CCRC UCM view to any read-only stream or while attempting to create an integration view on a multi-stream project: Unable to fetch delivery target stream Note: A read-only stream does not have a deliver target stream; however, CCRC should allow the creation of a view based on a read-only stream. This issue has been logged as defect APAR PK11770.

Solution

This issue has been resolved in ClearCase 7.0. This functionality will not be patched in prior versions and there are no known workarounds.

CCRC client install hangs on RedHat 8 platforms

This technote explains why the IBM® Rational® ClearCase® Remote Client (CCRC) install hangs on RedHat® Linux™ 8 platforms.

Cause

This problem has been logged as defect APAR PK03544.

Solution

Red Hat 8 is not a supported platform for CCRC clients. Review the technote 1205629 for more information on getting started with CCRC including links to documentation.

Unable to access a VOB directory when using CCRC

When using IBM® Rational® ClearCase® Remote Client (CCRC), accessing a directory that is loaded in a view will fail if the directory contains an element that is not selected by any rules in the view's the config spec.

Cause

After loading a sub-directory into a view, where all but one element is selected by a rule in the view's config spec, the entire directory is not accessible. The expected behavior is that the element name would appear in the view, with "no version selected" noted in the rule column. This issue can impact the entire VOB directory. For example, if no rule in the config spec selects the lost+found directory of the VOB, then that entire directory structure is not accessible in that view. This behavior has been reported as defect APAR IC47351.

Solution

This issue has been resolved in ClearCase 7.0. When an element is not matched by a config spec rule in the case of a -none rule or just simply not being selected by any rule: An error code is not generated by the CCRC server An entry for the element is not returned to the client (or visible in the view) The client will list any other siblings located in that sub-directory as expected WORKAROUND: The rules in the view's config spec must select all versions in all VOB sub-directories that are getting loaded into the view.

Sticky bit on AIX set to /tmp using CCRC causes disk to fill up with temporary files

This technote identifies a defect that impacts IBM® AIX® hosts running Rational® ClearCase® Remote Client (CCRC) causing the /tmp directory to fill up.

Cause

A sticky bit was applied by an administrator to /tmp on an AIX host running Rational Web Platform (RWP) in order to prevent users from deleting each other's temp files. This caused the ClearCase Remote Client (CCRC) to create temporary files during add to source operations named aaaa* in /tmp (example: /tmp/aaaaaaa). CCRC is unable to properly remove these files due to the permissions applied on /tmp thus the directory fills up causing loss of disk space. This has been reported as defect APAR IC48694.

Solution

This defect has been resolved in the following updates: Full ClearCase ClearCase LT 7.0 7.0.0.0-RATL-RCC-IFIX01 7.0.0.0-RATL-RCCLT-F001 2003.06.00 UNIX clearcase_p2003.06.00-38 clearcase_lt_p2003.06.00-18 After installation of the patch, ClearCase will create a directory underneath /tmp for RWP and CCWeb/CCRC to use. Since the sticky bit will not propagate its permissions to the new directory, RWP will work without leaving the aaaaa* files around. WORKAROUND: Create a script and or cronjob to delete these files from the /tmp directory on a scheduled basis to maintain control of disk space.

Modified date field displays undefined

This technote identifies a defect where the IBM® Rational® Web Platforms modification display time is undefined if the Regional Option is not set to English(United States) on Windows® affecting users of ClearCase Web and ClearCase Remote Client.

Cause

Defect APAR IC41616 has been reported to address this behavior.

Solution

This issue has been resolved in ClearCase 7.0, and there are no known workarounds.

CCRC Load state: Update Cancelled mode

This technote identifies a defect using the IBM® Rational® ClearCase® remote Client (CCRC) version 6.14.7 on Windows® XP where editing the config spec causes the view to be unusable.

Cause

Upon editing the config spec in CCRC and updating the view the view properties show the view in the following state: Load state: Update cancelled As a result, subsequent commands on this view cannot be run. This problem has been identified as defect RATLC01104132.

Solution

This defect has been resolved indirectly as of the changes made for update 6.14.8. Review technote 1215611 for more details on Installing or updating CCRC for Eclipse 3.0 and later.

Drag and drop from the host OS into CCRC fails

This technote identifies a defect where the drag and drop capability of copying files from the host operating system (OS) into the IBM® Rational® ClearCase® Remote Client (CCRC) fails, and provides steps to workaround the issue.

Symptom

Cause

Attempts to drag and drop files from the host OS into the CCRC Navigator view result in no files copied. Example: Attempts to drag eclipse.ini from the Microsoft® Windows® Explorer IDE into the CCRC Navigator view does not work even though all appearances shows that CCRC will accept the file. Drag the file from the source folder and drop into the destination folder in CCRC.  No File appears after the drop is complete. This problem has been identified as defect APAR PK30651.

Resolving the problem

This defect has been resolved in Rational ClearCase version 7.0.1. WORKAROUNDS: 1. Copy or move the file to the local view root from the host OS and refresh CCRC view. Example: Open Windows Explorer to the CCRC view root Perform the drag and drop function within that IDE Refresh CCRC 2. Perform the drag and drop by holding down the control key (Ctrl) while releasing (dropping) the file in the destination folder within CCRC. This will permit the copy of host OS files to CCRC Navigator view. Example: Attempts to drag eclipse.ini from the Microsoft® Windows® Explorer IDE into the CCRC Navigator view. Open Windows Explorer to the source folder. Drag the file to the destination folder within CCRC. Hold down the Ctrl key and drop the file in the destination folder. CCRC will request confirmation of the copy operation. Click Yes. CCRC will automatically refresh and the file will appear in CCRC. Change request (RFE) RATLC00742703 has also been filed to add the drag and drop functionality in to CCRC Details view. Currently this feature is disabled. Attempt to drop files into the Details view results in the icon below.

ccweb: Error: No tag in region for view

This technote identifies an IBM® Rational® ClearCase® defect relating to error ccweb: Error: No tag in region for view being reported when attempting to checkout an element in a view that is tagged in a region that is different than the region of the web server and provides you with information on how to workaround the issue.   Symptom If an element is checked out in a view that is tagged in a region that is different than the region of the CCRC web server (Rational Web Platform - RWP), attempts to launch the version tree browser from CCRC results in the following error: ccweb: Error: No tag in region for view             "2d5966b3.372511da.9b8b.00:01:80:a1:4b:fd".         ccweb: Error: INTERNAL ERROR detected and logged in "/var/adm/rational/clearcase/log/error_log".        ccweb: Error: INTERNAL ERROR detected and logged in "/var/adm/rational/clearcase/log/error_log".      After clearing the message, the version tree then comes up.

Cause

Defect APAR PK53146 has been opened to investigate this issue. To be added to the list of clients reporting this issue, contact IBM Rational ClearCase support.

Resolving the problem

The defect has been resolved in the following updates: 7.0.1 ClearCase LT Version 7.0.1.2 ClearCase Version 7.0.1.2 WORKAROUND: If you are not able to upgrade, then one workaround for this is to uncheckout the element and launch the version tree browser.

Error Fetching View Content

This technote details a known defect related to the error, Operation view_readdir_ext() failed: directory not selected in configuration specification, while attempting to refresh an IBM® Rational® ClearCase® Remote Client (CCRC) view that has not been updated first.

Symptom

Attempts to refresh a CCRC view, results in the following error: Error Fetching View Content An error was received from the server while retrieving view data. An error is also reported on the CCRC server: Operation view_readdir_ext() failed: directory not selected in configuration specification

Cause

This occurs because events similar to the following sequence have occurred in the environment: Create a folder in a VOB on the server; and do not put anything in it; leave it empty; Load this folder into a CCRC view. Set your filters to show non-loaded elements. Select the empty folder in the Navigator. Back on the server, create an object in the folder, and add it to source control. Back in the CCRC view, hit Refresh or simply click the empty folder again to get the above errors. Note: This issue does not occur in a view that does not have the directory loaded. Clicking the folder will show its contents as not loaded and without any errors, which is the expected behavior. This issue has been recorded as a defect, APAR PK33655.

Resolving the problem

This issue is related to unimplemented functionality in the current release, thus the problem has been closed as a request for enhancement. WORKAROUND: Update the CCRC view, rather than using the Refresh.

Error: 1 config spec load rule problems encountered

This technote identifies a defect where attempts to perform an IBM® Rational® ClearCase® UCM rebase (or deliver) operation from the ClearCase Remote Client (CCRC) results in the error Problems were encountered while retrieving view synchronization information and data..

Symptom

Attempts to start a UCM rebase operation from the ClearCase Remote Client results in the following error: Problems were encountered while retrieving view synchronization information and data. ccweb: Error: Unable to lookup " " in "@@": No such file or directory. ccweb: Error: Unable to access "": No such file or directory. ccweb: Error: 1 config spec load rule problems encountered. Problems were encountered while retrieving view synchronization information and data. Screenshot: Note: A similar error can occur when performing a deliver operation as well, especially when refactoring Java files.

Cause

The load rules of your view specify a directory to load which will no longer be visible as a result of the rebase. For example, if your view is configured to load DIR1 which resides in Component 1, but the latest baseline created now excludes Component 1 from the project, you will be unable to load DIR1 after the rebase is complete. This behavior has been reported as defect APAR PK09596.

Resolving the problem

This defect has been resolved in ClearCase version 7.0.1 WORKAROUND: The rebase operation will continue to fail until you change your load rules. Right click on the view in CCRC and choose Tools > Show ClearCase View Configuration. Inspect your load rules and compare them with the directory structure of your target stream (for example, use the integration stream if rebasing to the default target). If the directory specified in the error message is selected by your load rules, but does not exist on the integration stream, change the load rules accordingly.

Error 1334. The file mergemodule.txt cannot be installed

This technote identifies a defect that affect the IBM® Rational® ClearCase® Remote Client (CCRC) install for Microsoft® VS.NET

Symptom

Download ClearCase 7.0. Attempts to create a release area for the CCRC.NET integration using siteprep results in the following error: IBM Rational ClearCase Remote Client for VS.NET Install Error 1334. The file  'mergemodule.txt.xxx1234...' cannot be installed because the file cannot be found in cabinet file 'vc_atl70.CAB'.  This could indicate a network error, an error reading from the CD-ROM, or a problem with this package. (screenshot)

Cause

The install currently cannot be automated for the enduser. Defect APAR PK26377 has been submitted to address this problem.

Resolving the problem

This defect has been resolved in Rational ClearCase version 7.0.1. WORKAROUND: Install the CCRC.NET client by answering the several install questions posed during installation.

CCRC Web server URL is removed if all views are removed

This technote identifies a known defect that causes the connection information to the Rational Web Platform (RWP) server be lost when using the IBM® Rational® ClearCase® Remote Client (CCRC) interface.

Symptom

When all of your CCRC web views are removed, the copy area or view root for each view is also removed. This will delete the local path entry within the .ccase_wvreg file for each view. This file is where the CCRC Web server URL is cached; however, when the last view is removed, the URL is no longer referenced. Scenario: Log into CCRC, then log out (or Close CCRC) Restart CCRC and notice the URL is remembered Remove all your views Restart CCRC and notice the URL is no longer remembered

Cause

Defect APAR PK43874 has been submitted to address this behavior.

Resolving the problem

There is currently no solution available for this defect. WORKAROUND: At least one view must be maintained, and not removed, to prevent the URL from being removed.

CCRC fails to import projects from Team Project Set File (.psf) if Project Name starts with a VOB tag

This technote identifies an defect relating to Importing Team Project Files created from projects loaded through the IBM® Rational® ClearCase® Remote Client (CCRC) and provides you with information on how to workaround the issue.   Symptom

Cause

Importing Team Project Files created from projects loaded through the ClearCase Remote Client (CCRC) fails to load those projects where the name starts with the VOB tag. Example: The VOB tag is \RSA_VOB Within the VOB a directory Sources is created: \RSA_VOB\Sources The view is located in E:\views\ccrc_copyarea In Rational Software Architect (RSA), create four Java Projects called: RSA_VOBTest1 AnRSA_VOBTest RSA_VOBAnother Test1 The following projects will be imported into the workspace without errors. AnRSA_VOBTest Test1 The projects whose name starts with the VOB Tag instead will give the errors: Title: ------- Import project Set From ClearCase Message: ------- Directory  E:\views\ccrc_copyarea\RSA_VOBAnother does not contain an Eclipse project file Title: ------- Import project Set From ClearCase Message: ------- Directory  E:\views\ccrc_copyarea\RSA_VOBTest1 does not contain an Eclipse project file. Defect APAR PK29761 has been opened to address this issue.

Resolving the problem

There is currently no solution for this defect. WORKAROUND: Import the projects whose name starts with the VOB tag name one by one using the menu: File > Import Existing Project into Workspace

ClearCase Remote Client startup error on Linux

This technote identifies a defect where starting the rich client platform version of the IBM® Rational® ClearCase® Remote Client (CCRC) version 7.0 on Linux® results in an Eclipse™ error message causing CCRC to fail.

Symptom

Attempts to run CCRC 7.0 on Linux results in the following error message: Note: This error will pop up after the CCRC splash screen disappears: An error has occurred. See the log file /home/user/.Rational/CCRC/workspace/.metadata/.log The log file contains the following: !SESSION 2006-12-01 15:47:04.876 ----------------------------------------------- eclipse.buildId=M20050929-0840 java.fullversion=J2RE 1.4.2 IBM J9 2.2 Linux x86-32 j9xia32142-20050609  (JIT enabled) J9VM - 20050524_1738_lHdSMR JIT - r7_level20050518_1803 BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US Command-line arguments: -os linux -ws gtk -arch x86 !ENTRY org.eclipse.osgi 2006-12-01 15:47:12.606 !MESSAGE Application error !STACK 1 org.eclipse.swt.SWTError: XPCOM error -2147467262 at org.eclipse.swt.browser.Browser.error(Browser.java:996) at org.eclipse.swt.browser.Browser.setText(Browser.java:1456) at org.eclipse.ui.internal.intro.impl.presentations. BrowserIntroPartImplementation.generateDynamicContentForPage (BrowserIntroPartImplementation.java:215) at org.eclipse.ui.internal.intro.impl.presentations. BrowserIntroPartImplementation.dynamicStandbyStateChanged (BrowserIntroPartImplementation.java:395) at org.eclipse.ui.internal.intro.impl.presentations. BrowserIntroPartImplementation.doStandbyStateChanged (BrowserIntroPartImplementation.java:602) at org.eclipse.ui.internal.intro.impl.model.AbstractIntroPartImplementation. standbyStateChanged(AbstractIntroPartImplementation.java:249) at org.eclipse.ui.internal.intro.impl.model.IntroPartPresentation. standbyStateChanged(IntroPartPresentation.java:433) at org.eclipse.ui.intro.config.CustomizableIntroPart. standbyStateChanged(CustomizableIntroPart.java:263) at org.eclipse.ui.internal.ViewIntroAdapterPart$2. run(ViewIntroAdapterPart.java:74) at org.eclipse.swt.custom.BusyIndicator.showWhile (BusyIndicator.java:69) at org.eclipse.ui.internal.ViewIntroAdapterPart. setStandby(ViewIntroAdapterPart.java:70) at org.eclipse.ui.internal.ViewIntroAdapterPart$1.propertyChanged (ViewIntroAdapterPart.java:55) at org.eclipse.ui.internal.WorkbenchPartReference.fireInternalPropertyChange (WorkbenchPartReference.java:336) at org.eclipse.ui.internal.WorkbenchPartReference.fireZoomChange (WorkbenchPartReference.java:497) at org.eclipse.ui.internal.PartPane.setZoomed(PartPane.java:325) at org.eclipse.ui.internal.PartStack.setZoomed(PartStack.java:1191) at org.eclipse.ui.internal.PartSashContainer.zoomIn(PartSashContainer.java:827) at org.eclipse.ui.internal.PartSashContainer.childRequestZoomIn (PartSashContainer.java:848) at org.eclipse.ui.internal.LayoutPart.requestZoomIn(LayoutPart.java:356) at org.eclipse.ui.internal.PartStack.childRequestZoomIn(PartStack.java:1141) at org.eclipse.ui.internal.LayoutPart.requestZoomIn(LayoutPart.java:356) at org.eclipse.ui.internal.PerspectiveHelper.zoomIn (PerspectiveHelper.java:1289) at org.eclipse.ui.internal.WorkbenchPage.setState(WorkbenchPage.java:3299) at org.eclipse.ui.internal.WorkbenchPage.toggleZoom(WorkbenchPage.java:3345) at org.eclipse.ui.internal.WorkbenchIntroManager.setIntroStandby (WorkbenchIntroManager.java:193) at org.eclipse.ui.internal.WorkbenchIntroManager.showIntro (WorkbenchIntroManager.java:132) at org.eclipse.ui.application.WorkbenchAdvisor.openIntro (WorkbenchAdvisor.java:486) at org.eclipse.ui.internal.application.CompatibilityWorkbenchWindowAdvisor. openIntro(CompatibilityWorkbenchWindowAdvisor.java:57) at org.eclipse.ui.internal.WorkbenchWindow.open(WorkbenchWindow.java:699) at org.eclipse.ui.internal.Workbench.busyOpenWorkbenchWindow (Workbench.java:677) at org.eclipse.ui.internal.Workbench.doOpenFirstTimeWindow(Workbench.java:1282) at org.eclipse.ui.internal.Workbench.openFirstTimeWindow(Workbench.java:1223) at org.eclipse.ui.internal.WorkbenchConfigurer.openFirstTimeWindow (WorkbenchConfigurer.java:190) at org.eclipse.ui.application.WorkbenchAdvisor.openWindows (WorkbenchAdvisor.java:706) at org.eclipse.ui.internal.Workbench.init(Workbench.java:1034) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1636) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:367) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:143) at com.ibm.rational.clearcase.standalone.plugin.StandaloneApplication. run(StandaloneApplication.java:46) at org.eclipse.core.internal.runtime.PlatformActivator$1. run(PlatformActivator.java:226) at org.eclipse.core.runtime.adaptor.EclipseStarter. run(EclipseStarter.java:376) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:163) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:85) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:58) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:60) at java.lang.reflect.Method.invoke(Method.java:391) at org.eclipse.core.launcher.Main.invokeFramework(Main.java:334) at org.eclipse.core.launcher.Main.basicRun(Main.java:278) at org.eclipse.core.launcher.Main.run(Main.java:973) at org.eclipse.core.launcher.Main.main(Main.java:948) Note: The issue is present only in the rich client platform version of CCRC, and not in 3.2.1 Eclipse SDK plugin on the same system.

Cause

The cause appears to be related to an Eclipse defect. Review eclipse bug for more details:https://bugs.eclipse.org/bugs/show_bug.cgi?id=133304

Resolving the problem

WORKAROUND: Set the MOZILLA_FIVE_HOME environment variable to /nowhere before starting CCRC. setenv MOZILLA_FIVE_HOME /nowhere  Note: The sytax required to set the variable will depend on the shell in use.

Merge, diff and compare do not display when executed from CCRC on Linux

This technote explains why IBM® Rational® ClearCase® Remote Client (CCRC) windows are not being displayed when performing such operations as merge, diff and compare on Linux®.   Symptom The following is a list of the various symptoms that have been reported. There does not appear to be any error messages reported and the only symptom observed is the non-display of the necessary windows. CCRC window not displaying during compare with predecessor CCRC window not displaying during a checkin when a merge is required Windows not displaying when executing the following utilities from within CCRC Merge Diff Compare and potentially others from within CCRC This issue has only been reported on Linux but could also be experienced on other UNIX® clients.

Cause

OpenMotif 2.3 is installed on the client which utilizes new naming conventions for libXm and libMrm libraries that xclearcase does not recognize. Defect APAR PK60667 has been opened to investigate this issue.

Resolving the problem

There is no resolution for this defect at this time. WORKAROUND: Install OpenMotif 2.2

Undo checkout in CCRC fails due to post-op trigger that performs rmbranch

This technote identifies a defect that affects IBM® Rational® ClearCase® Remote Client (CCRC) users where attempts to uncheckout a version that fires a post operation trigger which removes any branchs with a zero version results in the error ccweb: Error: Unable to lookup "" in "": no version selected in configuration specification..   Symptom Attempts to perform an uncheckout where a post-op trigger fires to remove a branch that has zero versions results in the following error: Problems performing uncheckout Removed branch "@@". Checkout cancelled for "". ccweb: Error: Unable to lookup "" in  "": no version selected in configuration specification. ccweb: Error: Unable to access "":   no version selected in configuration specification. ccweb: Error: Problem downloading uncheckout of "": error detected by ClearCase subsystem"

Cause

This issue was identified as a product defect under APAR IC45546.

Resolving the problem

This defect has been resolved in Rational ClearCase version 7.0.1. WORKAROUNDS: Remove the trigger until the defect is resolved. Restrict the trigger from firing for CCRC users by using the -nuser switch when changing the mktrtype options. Review IBM Rational ClearCase Command Reference on the topic of mktrtype (cleartool man mktrtype) for more details.

RSA/RAD 7.0 .compatibility file constantly needs checkout/checkin within CCRC 7.0.1

This technote identifies a defect affecting the IBM® Rational® ClearCase® Remote Client (CCRC) where the .compatibility file is constantly checkedout and checked-in from the Rational Software Architect (RSA) and Rational Application Developer (RAD) 7.0 applications.   Symptom While sharing RAD projects within a team, you are required to checkout the.compatibility file constantly.

Cause

Defect RATLC01159075 has been submitted to address this issue.

Resolving the problem

There is currently no solution for this defect. WORKAROUND: Checkout and check-in the files as requested. Make required changes to the project. Manually merge the changes in the .compatibility file. Refer to technote 1247619 for further information about the.compatibility file.

Use Cancel when stopping a Delete operation in the Select Activity window

This technote identifies a defect in IBM® Rational® ClearCase® Remote Client where pressing the close, X, button on the Select Activities window when deleting an element incorrectly proceeds with the file removal when it should act the same as clicking Cancel (to stop the delete operation).   Symptom When you right-click a file in CCRC and choose Edit > Delete, then pressYes to the first dialog, it brings up the Select Activity window. From this window, if you select an activity from the drop-down list, then click the close (X) button at the top right of that window to close the window, the action is not cancelled (as expected), instead it proceeds as if "OK" were clicked and deletes the file.

Cause

Defect APAR PK61606 has been opened to investigate this issue. To be added to the list of clients reporting this issue, contact IBM Rational ClearCase support.

Diagnosing the problem

Problem Scenario: Attempt to delete a file from a CCRC view Click Yes when prompted with Delete Resources Confirmation. Select an Activity from the drop-down list, then click the X button to close the Select Activity window when prompted. The following message is displayed and the file is deleted.

Resolving the problem

There is currently no resolution available for this defect. WORKAROUND: Use Cancel on the Select Activity dialog box instead of the X button to close the window to cancel the deletion of the file, rather than proceed with the removal operation. Note: If there is no activity selected in the drop-down, then the close, X, button performs as it should and closes the dialog, and no delete operation is performed.