Interim fix CLM_601_iFix001.zip This interim fix is only valid for the Rational solution for Collaborative Lifecycle Management (CLM) 6.0.1 release. The Rational solution for CLM 6.0.2 is the next release that will include all these fixes. If you plan to upgrade, upgrade to version 6.0.2 or later. CONTENTS OF THIS INTERIM FIX 1. This readme file: readme.txt 2. Server patch file: CLM_server_patch_6.0.1.0-CALM601M-I20151217-2117.zip (see the SERVER PATCH INSTRUCTIONS section) 3. Jazz Reporting Service (Report Builder) patch file: rs.war (see the JAZZ REPORTING SERVICE INSTRUCTIONS section) 4. Data Collection Component mapping patch file: com.ibm.rational.rrdi.dcc.mapping_5.0.0.v20151217_0334.zip (see the DATA COLLECTION COMPONENT INSTRUCTIONS section) 5. Lifecycle Query Engine patch file: lqe.war (see the LIFECYCLE QUERY ENGINE AND LINK INDEX PROVIDER INSTRUCTIONS section) 6. Link Index Provider patch file: ldx.war (see the LIFECYCLE QUERY ENGINE AND LINK INDEX PROVIDER INSTRUCTIONS section) 7. Rational Team Concert Client for Eclipse update site: UpdateSiteFor_6.0.1.0-CALM601M-I20151217-2117.zip (see the RATIONAL TEAM CONCERT CLIENT FOR ECLIPSE UPDATE SITE INSTRUCTIONS section) In addition to the fixes listed in this readme file, the interim fix might also contain fixes for security issues. For details, see the IBM Product Security Incident Response Blog: https://www.ibm.com/connections/blogs/PSIRT/tags/psirtrational CONTENTS OF THIS FILE 1. SERVER PATCH INSTRUCTIONS 2. JAZZ REPORTING SERVICE (REPORT BUILDER) INSTRUCTIONS 3. DATA COLLECTION COMPONENT INSTRUCTIONS 4. LIFECYCLE QUERY ENGINE AND LINK INDEX PROVIDER INSTRUCTIONS 5. RATIONAL TEAM CONCERT CLIENT FOR ECLIPSE UPDATE SITE INSTRUCTIONS 6. ADDITIONAL FIXES INSTRUCTIONS 7. APAR FIXES 8. CLIENT APAR FIXES 9. KNOWN ISSUES 1. SERVER PATCH INSTRUCTIONS Note: -The CLM server patch file, CLM_server_patch_6.0.1.0-CALM601M-I20151217-2117.zip, might contain fixes for either a subset or all of these applications: Jazz Team Server, Rational Team Concert, Rational Quality Manager, Rational DOORS Next Generation, Data Collection Component, Rational Engineering Lifecycle Manager, CLM Server Monitoring. For the list of APARs that were fixed, listed by application, see the APAR FIXES section. -Before you install the server patch file, CLM_server_patch_6.0.1.0-CALM601M-I20151217-2117.zip, verify that no other test fixes or hot fixes are installed. If other fixes are installed, contact IBM Software Support. -For a CLM deployment on a single server, complete the following steps once. For a distributed CLM deployment, complete the same steps on each server. To install the server patch: a. Stop the CLM server. b. Verify whether the following directory exists: /server/patch. -If the directory exists, back up and then remove its contents. -If the directory does not exist, create it. c. Copy the server patch file, CLM_server_patch_6.0.1.0-CALM601M-I20151217-2117.zip, into the /server/patch directory. d. Clear the application server cache. For instructions on clearing the cache, consult the application server's detailed documentation. For instructions on what to remove, see the "To clear the application cache on WebSphere Application Server", "To clear the application cache on Liberty Profile" and "To clear the application cache on Apache Tomcat" sections in this file. e. Start the CLM server. f. Run repotools- -clean for each application that is installed to clear the repotools cache. Note: This will also display the help output. For instance: - repotools-jts -clean - repotools-ccm -clean - repotools-qm -clean - repotools-rm -clean Note: For a distributed CLM deployment, complete the same steps on each server, including the DCC server, if the DCC component exists on a separate machine. To uninstall the server patch: a. Stop the CLM server. b. Back up and then remove the contents of the following directory: /server/patch c. Clear the application server cache. For instructions on clearing the cache, consult the application server's detailed documentation. For instructions on what to remove, see the "To clear the application cache on WebSphere Application Server", "To clear the application cache on Liberty Profile" and "To clear the application cache on Apache Tomcat" sections in this file. d. Start the CLM server. e. Run repotools- -clean for each application that is installed. Note: This will also display the help output. For instance: - repotools-jts -clean - repotools-ccm -clean - repotools-qm -clean - repotools-rm -clean To clear the application cache on WebSphere Application Server: Remove the contents from these directories under the profile root, except for the noted help directory: temp, tranlog, wstemp, workspace. Note: Do not remove this directory, which is required for the CLM local help: temp/{jts_node}/{jts_server}/clmhelp_war. To clear the application cache on Liberty Profile: We have not identified the need to clear any cache in Liberty Profile To clear the application cache on Apache Tomcat: Remove the contents from these directories under the tomcat root, except for the noted help directory: temp, work. Note: Do not remove this directory, which is required for the CLM local help: work/Catalina/localhost/clmhelp. To validate that the server patch was successfully installed or uninstalled: a. After the server starts, open a CLM application. b. Click Help > About the Server. c. In the Build Information section, review the interim fix information to confirm that it is either installed (listed) or uninstalled (not listed). 2. JAZZ REPORTING SERVICE (REPORT BUILDER) INSTRUCTIONS To install the patch with Jazz Reporting Service (Report Builder) deployed on WebSphere Application Server: Option 1: Using the WebSphere Application Server scripting tool (wsadmin) a. Open a command window and navigate to the WebSphere profile bin directory (e.g. //profiles//bin). b. Execute the following command, ensuring that the WebSphere Application Server is running: Windows: wsadmin -language jython -user -password -f /server/was/clm_update.py> Linux: ./wsadmin.sh -language jython -user -password -f /server/was/clm_update.py> NOTE: This will update all applications with war files from the iFixPatch directory specified Option 2: Using the WebSphere Application Server Admin Console a. In the WebSphere Application Server Admin Console, stop the Jazz Reporting Service: Click Applications > Application Types > WebSphere enterprise applications, select the rs_war check box, and click Stop. b. Update the rs_war file: Select the rs_war check box and click Update. c. Select "Replace the entire application," browse to the new rs.war file in the location that you extracted it to, and click Next. d. Follow the Fast Path installation, and accept all of the default values. e. After the update is complete, save the configuration changes when you are prompted to. f. Start the Jazz Reporting Service: Select the rs_war check box and click Start. To uninstall the patch with Jazz Reporting Service (Report Builder) deployed on WebSphere Application Server: Option 1: Using the WebSphere Application Server scripting tool (wsadmin) a. Locate the rs.war file in the original Jazz Reporting Service installation. If there are other war files in this directory, copy the war files that you want to update to a new temporary folder (the clm_update.py script updates all applications with war files in the directory specified). a. Open a command window and navigate to the WebSphere profile bin directory (e.g. //profiles//bin). b. Execute the following command, ensuring that the WebSphere Application Server is running: Windows: wsadmin -language jython -user -password -f /server/was/clm_update.py> /server/webapps> Linux: ./wsadmin.sh -language jython -user -password -f /server/was/clm_update.py> /server/webapps> Option 2: Using the WebSphere Application Server Admin Console a. Locate the rs.war file in the original Jazz Reporting Service installation. b. In the WebSphere Application Server Admin Console, stop the Jazz Reporting Service: Click Applications > Application Types > WebSphere enterprise applications, select the rs_war check box, and click Stop. c. Update the rs_war file: Select the rs_war check box and click Update. d. Select "Replace the entire application," browse to the rs.war file in the original installation location, and click Next. e. Follow the Fast Path installation, and accept all of the default values. f. After the update is complete, save the configuration changes when you are prompted to. g. Start the Jazz Reporting Service: Select the rs_war check box and click Start. To install the patch with Jazz Reporting Service (Report Builder) deployed on Liberty Profile: a. Rename the new rs.war file as rs.war.zip. b. Stop the Liberty Profile server for the Jazz Reporting Service. c. Back up the following file in case you need to revert the patch: \server\liberty\servers\clm\apps\rs.war.zip d. Delete the following files: \server\liberty\servers\clm\apps\rs.war.zip \server\liberty\clmServerTemplate\apps\rs.war.zip e. Delete the following directories: \server\liberty\servers\clm\apps\rs.war \server\liberty\clmServerTemplate\apps\rs.war f. Place the new rs.war.zip file in the following directories: \server\liberty\servers\clm\apps \server\liberty\clmServerTemplate\apps g. Unzip the new rs.war.zip file into the following directories: \server\liberty\servers\clm\apps\rs.war \server\liberty\clmServerTemplate\apps\rs.war h. Start the server. To uninstall the patch with Jazz Reporting Service (Report Builder) deployed on Liberty Profile server: a. Stop the Liberty Profile server for the Jazz Reporting Service. b. Restore the original rs.war.zip file that was backed up during the installation to the following directories: \server\liberty\servers\clm\apps \server\liberty\clmServerTemplate\apps c. Delete the following directories: \server\liberty\servers\clm\apps\rs.war \server\liberty\clmServerTemplate\apps\rs.war d. Unzip the original rs.war.zip file into the following directories: \server\liberty\servers\clm\apps\rs.war \server\liberty\clmServerTemplate\apps\rs.war e. Start the server. To install the patch with Jazz Reporting Service (Report Builder) deployed on Apache Tomcat: a. Stop the Apache Tomcat server for the Jazz Reporting Service. b. Back up the following file in case you need to revert the patch: \server\tomcat\webapps\rs.war c. Delete the following file: \server\tomcat\webapps\rs.war d. Delete the following directories: \server\tomcat\webapps\rs \server\tomcat\work\Catalina\localhost\rs e. Place the new rs.war file in the \server\tomcat\webapps directory. f. Start the server. To uninstall the patch with Jazz Reporting Service (Report Builder) deployed on Apache Tomcat server: a. Stop the Apache Tomcat server for the Jazz Reporting Service. b. Restore the original rs.war file that was backed up during the installation to the following directory: \server\tomcat\webapps\ c. Delete the following directories: \server\tomcat\webapps\rs \server\tomcat\work\Catalina\localhost\rs d. Start the server. To verify that the patch was successfully installed: a. After the server starts, open the Jazz Reporting Service home page. b. Click on the Admin link c. Click the question mark icon near the upper right. d. Select About Jazz Reporting Service. e. Check that the build ID in the dialog box is JRS_6.0.1-I20151216-2233 3. DATA COLLECTION COMPONENT INSTRUCTIONS To install the mapping patch for Data Collection Component: a. Back up all the files inside the \server\conf\dcc\mapping directory. b. Delete all the existing files from this directory. c. Extract the contents of the com.ibm.rational.rrdi.dcc.mapping_*.zip into this directory. d. Open the \server\conf\dcc\teamserver.properties file. e. Locate the com.ibm.rational.datacollection.initialized parameter, change its value to false, and save/close the file. For example: com.ibm.rational.datacollection.initialized=false f. Restart the DCC server. 4. LIFECYCLE QUERY ENGINE AND LINK INDEX PROVIDER INSTRUCTIONS If this is a new installation, a backup is not needed. Otherwise, be sure you have a backup before you install this interim fix. There has been no change to LQE metadata or index structure since V6.0, so there is no need to migrate your data. For details, see "Backing up and restoring Lifecycle Query Engine": http://www.ibm.com/support/knowledgecenter/SSYMRC_6.0.0/com.ibm.team.jp.lqe2.doc/topics/t_lqe_backup.html. To install the patch with Lifecycle Query Engine or Link Index Provider deployed on a WebSphere Application Server: Option 1: Using the WebSphere Application Server scripting tool (wsadmin) a. Open a command window and navigate to the WebSphere profile bin directory (e.g. //profiles//bin). b. Execute the following command, ensuring that the WebSphere Application Server is running: Windows: wsadmin -language jython -user -password -f /server/was/clm_update.py> Linux: ./wsadmin.sh -language jython -user -password -f /server/was/clm_update.py> NOTE: This will update all applications with war files from the iFixPatch directory specified Option 2: Using the WebSphere Application Server Admin Console a. Extract the lqe.war or ldx.war file to your local computer or on the Lifecycle Query Engine or Link Index Provider server. b. In the WebSphere Application Server Admin Console, stop the Lifecycle Query Engine or Link Index Provider application: Click Applications > Application Types > WebSphere enterprise applications, select the lqe_war or ldx_war check box, and click Stop. c. Update the lqe_war or ldx_war file: Select the lqe_war or ldx_war check box and click Update. d. Select "Replace the entire application," browse to the new lqe.war or ldx.war file in the location that you extracted it to, and click Next. e. Follow the Fast Path installation, and accept all of the default values. f. After the update is complete, save the configuration changes when you are prompted to. g. Start the Lifecycle Query Engine or Link Index Provider application: Select the lqe_war or ldx_war check box and click Start. To uninstall the patch with Lifecycle Query Engine or Link Index Provider deployed on a WebSphere Application Server: Option 1: Using the WebSphere Application Server scripting tool (wsadmin) a. Locate the lqe.war or ldx.war file in the original Jazz Reporting Service installation. If there are other war files in this directory, copy the war files that you want to update to a new temporary folder (the clm_update.py script updates all applications with war files in the directory specified). a. Open a command window and navigate to the WebSphere profile bin directory (e.g. //profiles//bin). b. Execute the following command, ensuring that the WebSphere Application Server is running: Windows: wsadmin -language jython -user -password -f /server/was/clm_update.py> /server/webapps> Linux: ./wsadmin.sh -language jython -user -password -f /server/was/clm_update.py> /server/webapps> Option 2: Using the WebSphere Application Server Admin Console a. Locate the lqe.war or ldx.war file in the original Lifecycle Query Engine or Link Index Provider installation. b. In the WebSphere Application Server Admin Console, stop the Lifecycle Query Engine or Link Index Provider application: Click Applications > Application Types > WebSphere enterprise applications, select the lqe_war or ldx_war check box, and click Stop. c. Update the lqe_war or ldx_war file: Select the lqe_war or ldx_war check box and click Update. d. Select "Replace the entire application," browse to the lqe.war or ldx.war file in the original installation location, and click Next. e. Follow the Fast Path installation, and accept all of the default values. f. After the update is complete, save the configuration changes when you are prompted to. g. Start the Lifecycle Query Engine or Link Index Provider application: Select the lqe_war or ldx_war check box and click Start. To install the patch with Lifecycle Query Engine or Link Index Provider deployed on Liberty Profile: a. Rename the new lqe.war or ldx.war file as lqe.war.zip or ldx.war.zip. b. Stop the Liberty Profile server for the Lifecycle Query Engine or Link Index Provider. c. Back up the following file in case you need to revert the patch: \server\liberty\servers\clm\apps\lqe.war.zip or \server\liberty\servers\clm\apps\ldx.war.zip d. Delete the following files: \server\liberty\servers\clm\apps\lqe.war.zip \server\liberty\clmServerTemplate\apps\lqe.war.zip or \server\liberty\servers\clm\apps\ldx.war.zip \server\liberty\clmServerTemplate\apps\ldx.war.zip e. Delete the following directories: \server\liberty\servers\clm\apps\lqe.war \server\liberty\clmServerTemplate\apps\lqe.war or \server\liberty\servers\clm\apps\ldx.war \server\liberty\clmServerTemplate\apps\ldx.war f. Place the new lqe.war.zip or ldx.war.zip file in the following directories: \server\liberty\servers\clm\apps \server\liberty\clmServerTemplate\apps or \server\liberty\servers\clm\apps \server\liberty\clmServerTemplate\apps g. Unzip the new lqe.war.zip or ldx.war.zip file into the following directories: \server\liberty\servers\clm\apps\lqe.war \server\liberty\clmServerTemplate\apps\lqe.war or \server\liberty\servers\clm\apps\ldx.war \server\liberty\clmServerTemplate\apps\ldx.war h. Start the server. To uninstall the patch with Lifecycle Query Engine or Link Index Provider deployed on Liberty Profile server: a. Stop the Liberty Profile server for the Lifecycle Query Engine or Link Index Provider. b. Restore the original lqe.war.zip or ldx.war.zip file that was backed up during the installation to the following directories: \server\liberty\servers\clm\apps \server\liberty\clmServerTemplate\apps or \server\liberty\servers\clm\apps \server\liberty\clmServerTemplate\apps c. Delete the following directories: \server\liberty\servers\clm\apps\lqe.war \server\liberty\clmServerTemplate\apps\lqe.war or \server\liberty\servers\clm\apps\ldx.war \server\liberty\clmServerTemplate\apps\ldx.war d. Unzip the original rs.war.zip file into the following directories: \server\liberty\servers\clm\apps\lqe.war \server\liberty\clmServerTemplate\apps\lqe.war or \server\liberty\servers\clm\apps\ldx.war \server\liberty\clmServerTemplate\apps\ldx.war e. Start the server. To install the patch when the Lifecycle Query Engine or Link Index Provider is deployed on Apache Tomcat: a. Stop the Apache Tomcat server for the Lifecycle Query Engine or Link Index Provider application. b. Back up the following file in case you need to revert the patch: \server\tomcat\webapps\lqe.war or \server\tomcat\webapps\ldx.war c. Delete the following file: \server\tomcat\webapps\lqe.war or \server\tomcat\webapps\ldx.war d. Delete the following directories: \server\tomcat\webapps\lqe or \server\tomcat\webapps\ldx \server\tomcat\work\Catalina\\lqe or \server\tomcat\work\Catalina\\ldx e. Place the new lqe.war or ldx.war file in the \server\tomcat\webapps directory or the \server\tomcat\webapps directory, respectively. f. Start the server. To uninstall the patch with Lifecycle Query Engine or Link Index Provider deployed on an Apache Tomcat server: a. Stop the Apache Tomcat server for the Lifecycle Query Engine or Link Index Provider application. b. Restore the original lqe.war or ldx.war file that was backed up during the installation to the following directory: \server\tomcat\webapps\ or \server\tomcat\webapps\ c. Delete the following directories: \server\tomcat\webapps\lqe or \server\tomcat\webapps\ldx \server\tomcat\work\Catalina\localhost\lqe or \server\tomcat\work\Catalina\localhost\ldx d. Start the server. To verify that the patch was successfully installed: a. After the server starts, open the Lifecycle Query Engine or Link Index Provider home page. b. Verify that the build ID in the upper right matches LQE_6.0.1-I20151209-2116. After installing the patch: a. The Lifecycle Query Engine or Link Index Provider automatically detects whether it is necessary to migrate data from an existing instance. If data migration is necessary, a Start Migration button is displayed on the main Lifecycle Query Engine or Link Index Provider page: https:///lqe/web/admin or https:///ldx/web/admin. If the button is displayed, click Start Migration. b. Reindex the data sources as required. 5. RATIONAL TEAM CONCERT CLIENT FOR ECLIPSE UPDATE SITE INSTRUCTIONS To install the client update site: a. Extract the update site file to the computer where the client is installed. b. In the Rational Team Concert client, click Help > Install New Software. c. In the Install window, click Add. d. In the Add Repository window, click Local and navigate to the extracted update site file. The update site root directory contains a site.xml file. e. Select the patches to install. f. If you agree to the terms, accept the license agreement and click Install. g. After the installation is complete, restart the Rational Team Concert client. To update the feature patch, you can install the new version directly over an old patch. You do not have to uninstall the old patch. To uninstall the client update site: a. In the Rational Team Concert client, click Help > About Rational Team Concert > Installation Details. b. Select the patches to uninstall and click Uninstall. c. After the uninstall process is complete, restart the Rational Team Concert client. WARNING: -The update site does not work with Rational Team Concert Client for Eclipse 3.6 that was installed by using IBM Installation Manager. Alternatively, you can use the Rational Team Concert Client for Eclipse 3.6 .zip installation, or you can use IBM Installation Manager to install the Rational Team Concert Client for Eclipse 4.2. -If you run the uninstall process on a Rational Team Concert client that was installed by using a .zip file, the feature patch will be removed along with the original feature. Removing the patch breaks the functionality of the affected feature. For a client that was installed by using a .zip file, reinstall the features by downloading the Rational Team Concert p2 repository from Jazz.net, and use the same installation steps with the following exception. For step d, click Archive and select the p2 repository .zip file and install the Rational Team Concert feature. This step removes the patched plug-ins and replaces the missing features with the original versions of the feature from the p2 repository. -If you run the uninstall process on a Rational Team Concert client that was installed by using the p2 repository, to remove the patch, you must uninstall the entire Rational Team Concert p2 feature and then reinstall the entire Rational Team Concert feature through the p2 repository. 6. ADDITIONAL FIXES INSTRUCTIONS No patch non-compliant work items found. 7. APAR FIXES This interim fix contains fixes for the following APARs: [APAR ID] [Maintenance Item Summary] [Maintenance Item URL] +-- Product Rational Engineering Lifecycle Manager Fixed in release 6.0.2: [APAR PI53450] [Performance issue when a system artifact container is linked to some containers] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/375968] [APAR PI53450] [RELM full text search cannot show non-versioned data correctly] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/376590] [APAR PI53450] [[Backport] Custom hover shows HTML tags which should be displayed as formatted text] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/377963] +-- Product Data Collection Component Fixed in release 6.0.2: [APAR PI52655] [[Backport 6.0.1] 375622: Delete Fact Table Data DCC job took long time but could not finish] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/376061] [APAR PI53450] [[Backport 6.0.1] 375126: DCC not available after doing a rename and then an upgrade to 6.0.1] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/375333] [APAR PI53450] [[Backport 6.0.1] DCC ETL Change and Configuration Management - Work Item Metrics fails when run against Oracle] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/375334] [APAR PI53810] [[Backport 6.0.1] Need scriptable way of setting DCC configuration commands] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/377664] +-- Product Lifecycle Query Engine Fixed in release 6.0.2: [APAR PI53450] [[Backport 6.0.1] lqe.BatchWriter[TRS 2.0 for QM Resources] failed with error] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/375769] +-- Product Rational Quality Manager Fixed in release 6.0.2: [APAR PI52469] [Execution schedules using build records from RQM 5.0.2 will not run after upgrade to 6.0] [https://jazz.net/jazz02/resource/itemName/com.ibm.team.workitem.WorkItem/145296] [APAR PI53450] [Archiving test result does not create deletion event for its step results in many places] [https://jazz.net/jazz02/resource/itemName/com.ibm.team.workitem.WorkItem/145074] [APAR PI53450] [Executing Test Suite in GUI is picking multiple target machines using NI adapter] [https://jazz.net/jazz02/resource/itemName/com.ibm.team.workitem.WorkItem/145075] [APAR PI53450] [TRS 2.0 for QM resources fail every 6 hours with error, requiring reindex] [https://jazz.net/jazz02/resource/itemName/com.ibm.team.workitem.WorkItem/145072] [APAR PI53450] [hide configuration resource shape in TRS] [https://jazz.net/jazz02/resource/itemName/com.ibm.team.workitem.WorkItem/145071] [APAR PI53450] [test environment's shape returns 500] [https://jazz.net/jazz02/resource/itemName/com.ibm.team.workitem.WorkItem/145073] [APAR TBD] [Rational Quality Manager cannot open selection dialogs if the OSLC provider provides selection dialogs but no creation dialogs] [https://jazz.net/jazz02/resource/itemName/com.ibm.team.workitem.WorkItem/145707] +-- Product Jazz Foundation Fixed in release 6.0.2: [APAR PI53432] [VVC import in DM failed with exception when exported data contains a change set with triplets without a resource object [6.0.1]] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/377289] [APAR PI53450] [ObjectMap.get(PojoFilter filter, String key) fails with ParseException[6.0.1]] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/377779] +-- Product Jazz Reporting Service Fixed in release 6.0.2: [APAR PI52228] [[Backport 6.0.1] The unparser should handle the INTERSECT clause] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/375754] [APAR PI53450] [[Backport 6.0.1] Advanced SPARQL query editor hangs if extra variables are added with shorter names] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/375759] [APAR PI53450] [[Backport 6.0.1] Self Host: Report Builder needs to be restarted or widgets fail to render] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/375761] [APAR PI53450] [[Backport 6.0.1] Some columns are spanning when they shouldn't] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/375758] [APAR PI53450] [[Backport 6.0.1] Specific SQL advanced query no longer editable after save and reload] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/375757] [APAR TBD] [[Backport 6.0.1] Copying db directory from existing server to new installation can cause ClassCastException] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/375762] [APAR TBD] [[Backport 6.0.1] NullPointerException after switching report type from Current Work Item Data to Historical Trends] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/375763] +-- Product Rational DOORS Next Generation Fixed in release 6.0.2: [APAR PI52669] [Query timeout during SuspectLinkIndexService.clearIndexedLinks could result in unbounded growth of RM on-disk indices] [https://jazz.net/jazz03/resource/itemName/com.ibm.team.workitem.WorkItem/102100] [APAR PI53450] [Describe queries return invalid data after server was renamed] [https://jazz.net/jazz03/resource/itemName/com.ibm.team.workitem.WorkItem/102357] [APAR PI53450] [Duplicate module can not be successfully completed.] [https://jazz.net/jazz03/resource/itemName/com.ibm.team.workitem.WorkItem/102272] [APAR PI53450] [Expanding and collapsing sections in a document is unusable.  Major scrolling issues] [https://jazz.net/jazz03/resource/itemName/com.ibm.team.workitem.WorkItem/102751] [APAR PI53450] [JRS: Cannot report against new local configurations created from a GC] [https://jazz.net/jazz03/resource/itemName/com.ibm.team.workitem.WorkItem/102692] [APAR PI53450] [JRS: Cannot report on module content in context of any other configuration after adding to/removing from/modifying artifacts in module] [https://jazz.net/jazz03/resource/itemName/com.ibm.team.workitem.WorkItem/102270] [APAR PI53450] [Link Validity: DM <-> RM - setting a link as valid in DM doesn't change the link status in RM] [https://jazz.net/jazz03/resource/itemName/com.ibm.team.workitem.WorkItem/102507] [APAR PI53450] [Linked artifacts in diagram editor do not "highlight" when the link is selected in link area AND links do not highlight when diagram artifact is selected (regression)] [https://jazz.net/jazz03/resource/itemName/com.ibm.team.workitem.WorkItem/102266] [APAR PI53450] [Module editing - editing new cell is flashy/jumpy] [https://jazz.net/jazz03/resource/itemName/com.ibm.team.workitem.WorkItem/102356] [APAR PI53450] [RRDG Report: Traceability says NONE for RM project that is not CM enabled] [https://jazz.net/jazz03/resource/itemName/com.ibm.team.workitem.WorkItem/102269] [APAR PI53450] [Server rename - comparison wizard does not display artifact content for modules after server rename] [https://jazz.net/jazz03/resource/itemName/com.ibm.team.workitem.WorkItem/102271] [APAR PI53450] [Slow TRS query when creating new stream or baseline] [https://jazz.net/jazz03/resource/itemName/com.ibm.team.workitem.WorkItem/102339] +-- Product Rational Team Concert Fixed in release 6.0.2: [APAR PI53025] [Performance problem during v4 to v6 migration - buildmap component UUID] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/376976] [APAR PI53411] [Migration of buildmap data from pre-4.0 through 6.0 can fail from malformed data] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/377638] [APAR PI53450] [Bulk Edit for tags do not update properly] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/376610] [APAR PI53450] [[6.0.1iFix] Backport fix for: "Code Review is showing the wrong version Id (at the top of the compare editor) for the before state pane when reviewing a change set that has merges"] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/376967] [APAR PI53450] [[Server Side]The value of Component condition can not be saved in SCD query] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/378016] 8. CLIENT APAR FIXES This client update site contains fixes for the following defects: [APAR ID] [Maintenance Item Summary] [Maintenance Item URL] +-- RTC Client Fixes Fixed in release 6.0.2: [APAR PI53450] [Getting NPE opening a buildmap when migrating from older versions] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/376606] [APAR PI53450] [NullPointerException trying to save CAS configuration] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/376605] [APAR PI53450] [[Client Side]The value of Component condition can not be saved in SCD query] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/376608] 9. KNOWN ISSUES None