Interim fix CLM_60_iFix002.zip This interim fix is only valid for the Rational solution for Collaborative Lifecycle Management (CLM) 6.0.0 release. The Rational solution for CLM 6.0.1 is the next release that will include these fixes. If you plan to upgrade, upgrade to version 6.0.1 or later. CONTENTS OF THIS INTERIM FIX 1. This readme file: readme.txt 2. Server patch file: CLM_server_patch_6.0.0.0-CALM60M-I20150730-2020.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. Lifecycle Query Engine patch file: lqe.war (see the LIFECYCLE QUERY ENGINE AND LINK INDEX PROVIDER INSTRUCTIONS section) 5. Link Index Provider patch file: ldx.war (see the LIFECYCLE QUERY ENGINE AND LINK INDEX PROVIDER INSTRUCTIONS section) 6. Rational Team Concert Client for Eclipse update site: UpdateSiteFor_6.0.0.0-CALM60M-I20150730-2020.zip (see the RATIONAL TEAM CONCERT CLIENT FOR ECLIPSE UPDATE SITE INSTRUCTIONS section) 7. Files required to resolve JRS APAR PI43630 - Failed to upgrade JRS if the root context was changed to SPARQL_Gateway during installation: app_upgrade.bat and app_upgrade.sh (see instructions below for APAR PI43630 in the ADDITIONAL FIXES INSTRUCTIONS) 8. WebSphere Application Server script file: clm_update.py (see the LIFECYCLE QUERY ENGINE AND LINK INDEX PROVIDER INSTRUCTIONS and JAZZ REPORTING SERVICE INSTRUCTIONS sections) 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. LIFECYCLE QUERY ENGINE AND LINK INDEX PROVIDER INSTRUCTIONS 4. RATIONAL TEAM CONCERT CLIENT FOR ECLIPSE UPDATE SITE INSTRUCTIONS 5. ADDITIONAL FIXES INSTRUCTIONS 6. APAR FIXES 7. CLIENT APAR FIXES 8. KNOWN ISSUES 1. SERVER PATCH INSTRUCTIONS Note: -The CLM server patch file, CLM_server_patch_6.0.0.0-CALM60M-I20150730-2020.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.0.0-CALM60M-I20150730-2020.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.0.0-CALM60M-I20150730-2020.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" and "To clear the application cache on Apache Tomcat" sections in this file. e. Start the CLM server. 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" and "To clear the application cache on Apache Tomcat" sections in this file. d. Start the CLM server. 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 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: Windows: wsadmin -language jython -user -password -f Linux: ./wsadmin.sh -language jython -user -password -f 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: 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 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 the question mark icon near the upper right. c. Select About Jazz Reporting Service (Report Builder). d. Check that the build ID in the dialog box is 6.0.0-I20150723-2130 3. 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: Windows: wsadmin -language jython -user -password -f Linux: ./wsadmin.sh -language jython -user -password -f 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: 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 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 6.0.0-I20150615-0927. 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. 4. 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. 5. ADDITIONAL FIXES INSTRUCTIONS +-- Product Lifecycle Query Engine Fixed in release 6.0.1: [APAR PI41292] [[Backport 6.0] LQE doesn't skip member errors as expected] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/358862] This defect requires additional steps to apply: see the LIFECYCLE QUERY ENGINE AND LINK INDEX PROVIDER INSTRUCTIONS section ---- +-- Product Jazz Foundation Fixed in release 6.0.1: [APAR PI44364] [VVC cache configurations missing after migration] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/362573] This defect requires additional steps to apply: You need only do this once per iFix. If you have already done these steps for another fix, you do not need to repeat them. 1. Go to the /server directory. 2. Execute the following command: repotools-jts -clean ---- +-- Product Jazz Reporting Service Fixed in release 6.0.1: [APAR PI42044] [[Backport 6.0] Widget category load fails with error "Failed to retrieve categories" when report tag has '&'] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/358876] This defect requires additional steps to apply: see the JAZZ REPORTING SERVICE INSTRUCTIONS section ---- [APAR PI43630] [[Backport 6.0] Apostrophe in meta data causes the report to show blank page] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/358864] This defect requires additional steps to apply: see the JAZZ REPORTING SERVICE INSTRUCTIONS section ---- [APAR PI43630] [[Backport 6.0] Calculated Attributes drill-through is not correctly showing the child work item ID, URL and Name] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/362425] This defect requires additional steps to apply: see the JAZZ REPORTING SERVICE INSTRUCTIONS section ---- [APAR PI43630] [[Backport 6.0] Failed to upgrade JRS if the root context was changed to SPARQL_Gateway during installation] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/358865] This defect requires additional steps to apply: Windows: Replace the existing file app_upgrade.bat in the /upgrade/ directory with the new version. Linux: Replace the existing file app_upgrade.sh in the /upgrade/ directory with the new version. ---- [APAR PI43630] [[Backport 6.0] Filed Against list in condition edit is corrupted] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/362422] This defect requires additional steps to apply: see the JAZZ REPORTING SERVICE INSTRUCTIONS section ---- [APAR PI43630] [[Backport 6.0] JRS server rename fails with multiple mapping events or if server is restarted during rename process] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/359968] This defect requires additional steps to apply: see the JAZZ REPORTING SERVICE INSTRUCTIONS section ---- [APAR PI43630] [[Backport 6.0] Parameter values for ready-to-use reports are escaped causing problems in case when special characters are present] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/360135] This defect requires additional steps to apply: see the JAZZ REPORTING SERVICE INSTRUCTIONS section ---- [APAR PI43630] [[Backport 6.0] Planned for condition with immediate children modifier after Filed Against condition - sometimes extra value added to json causing SQL error later] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/362423] This defect requires additional steps to apply: see the JAZZ REPORTING SERVICE INSTRUCTIONS section ---- [APAR PI43630] [[Backport 6.0] Special characters are not displayed properly in column names] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/358866] This defect requires additional steps to apply: see the JAZZ REPORTING SERVICE INSTRUCTIONS section ---- [APAR PI43630] [[Backport 6.0] Unnecessary word splitting in table compromises readability of table] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/358873] This defect requires additional steps to apply: see the JAZZ REPORTING SERVICE INSTRUCTIONS section ---- 6. APAR FIXES This interim fix contains fixes for the following APARs: [APAR ID] [Maintenance Item Summary] [Maintenance Item URL] +-- Product Jazz Security Architecture Single Sign-on Fixed in release 6.0.1: [APAR PI43630] [Fix for: JAS: Invalid userid is returned when user has "@" in username] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/359402] +-- Product Rational Engineering Lifecycle Manager Fixed in release 6.0.1: [APAR PI43630] [[Backport 6.0] ALM(Upgrade-Manual):- repotools-relm.bat doesnt work during manual upgrade] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/358860] +-- Product Data Collection Component Fixed in release 6.0.1: [APAR PI42419] [[Backport 6.0] DCC Quality Management job failing] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/358877] [APAR PI43630] [[Backport 6.0] DCC ETL does not handle default value properly for some mandatory field] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/362429] [APAR PI43701] [[Backport 6.0] CQPAR00143712: DCC handling of Oracle BINARY_DOUBE is wrong] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/361212] +-- Product Rational Quality Manager Fixed in release 6.0.1: [APAR PI42597] [IServerStatusRestService/databaseStatus service being called to get login page. Causing unnecessary delays when opening dashboards] [https://jazz.net/jazz02/resource/itemName/com.ibm.team.workitem.WorkItem/138190] [APAR PI43630] [Could not mark the "Actual Result" in the steps since the test data iteration 2 when executing TCER with Test Data] [https://jazz.net/jazz02/resource/itemName/com.ibm.team.workitem.WorkItem/138006] [APAR PI43630] [QM TRS feed stops working in long run] [https://jazz.net/jazz02/resource/itemName/com.ibm.team.workitem.WorkItem/138004] [APAR PI43630] [QM does not generate a modification event for a concept in TRS change log when modifying a test case] [https://jazz.net/jazz02/resource/itemName/com.ibm.team.workitem.WorkItem/138003] [APAR PI43630] [Saving manual merge result of a manual test script with requirement changes produced an error dialog] [https://jazz.net/jazz02/resource/itemName/com.ibm.team.workitem.WorkItem/138005] +-- Product Jazz Foundation Fixed in release 6.0.1: [APAR PI41335] [SimpleDateFormat is not thread safe and cannot be shared among threads (Extracting Work Items via reportable API can return wrong modification dates for history entries)] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/357589] [APAR PI43630] ["lqe_user" isn't added to the permission list of ldx in 60 iFixes] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/362978] [APAR PI43630] [6.0rc1 Update script does not migrate ccm.war and jts.war correctly - entries for custom ldap groups in web.xml missing (361154)] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/362776] [APAR PI43630] [Backport work item 361341 - LDX user permissions lost after startup.] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/361731] [APAR PI43630] [DCC is broken after running JTS setup wizard and DCC database is not Derby] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/360895] [APAR PI44364] [VVC cache configurations missing after migration] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/362573] +-- Product Rational DOORS Next Generation Fixed in release 6.0.1: [APAR PI40280] [Image Loading in Modules can push down selected artifact] [https://jazz.net/jazz03/resource/itemName/com.ibm.team.workitem.WorkItem/97926] [APAR PI40295] [com.hp.hpl.jena.shared.CannotEncodeCharacterException when importing CSV containing control characters] [https://jazz.net/jazz03/resource/itemName/com.ibm.team.workitem.WorkItem/97971] [APAR PI41498] [WellKnownTypeUrisCache fails with bad typesystem] [https://jazz.net/jazz03/resource/itemName/com.ibm.team.workitem.WorkItem/97571] [APAR PI43630] [CM - conflicts when a core artifact is removed in a stream and there is a conflicting edit in another stream can generate a warning that you cannot resolve in a module after delivery] [https://jazz.net/jazz03/resource/itemName/com.ibm.team.workitem.WorkItem/97967] [APAR PI43630] [Can't create any links if the RM artifact was created in 3.x (and not modified since 4.x). User sees a 400 Bad Request] [https://jazz.net/jazz03/resource/itemName/com.ibm.team.workitem.WorkItem/97724] [APAR PI43630] [Customer migration fails with DB2 SQL Error: SQLCODE=-302, SQLSTATE=22001] [https://jazz.net/jazz03/resource/itemName/com.ibm.team.workitem.WorkItem/97959] [APAR PI43630] [Data loss when creating objects in locked module] [https://jazz.net/jazz03/resource/itemName/com.ibm.team.workitem.WorkItem/98085] [APAR PI43630] [Generating a PDF from a text artifact is not working on selfhost] [https://jazz.net/jazz03/resource/itemName/com.ibm.team.workitem.WorkItem/98512] [APAR PI43630] [In an Opt-Out project, artifact picker dialogs (e.g., link, insert) shows all RM opt-out projects, even ones that I don't have access to] [https://jazz.net/jazz03/resource/itemName/com.ibm.team.workitem.WorkItem/97964] [APAR PI43630] [Migration fails with ValidationException] [https://jazz.net/jazz03/resource/itemName/com.ibm.team.workitem.WorkItem/98910] [APAR PI43630] [Module Usability: Contents jump around on screen when starting and ending edits.] [https://jazz.net/jazz03/resource/itemName/com.ibm.team.workitem.WorkItem/98046] [APAR PI43630] [WAS - Diagram tips hover hot spots not displayed correctly] [https://jazz.net/jazz03/resource/itemName/com.ibm.team.workitem.WorkItem/97969] [APAR PI43630] [Web client should not send concurrent requests to update the deliver session] [https://jazz.net/jazz03/resource/itemName/com.ibm.team.workitem.WorkItem/97965] [APAR PI43990] [Suspicion Profile Administration page does not show list of projects if Registered Application name for RM does not contain "rm"] [https://jazz.net/jazz03/resource/itemName/com.ibm.team.workitem.WorkItem/98522] [APAR PI44525] [RNDG 6.0 upgrade fails when module baseline title is empty] [https://jazz.net/jazz03/resource/itemName/com.ibm.team.workitem.WorkItem/98894] [APAR PI44847] [Not able to select OSLC link types as "Preferred link types" for artifact types when the RM project area has Configuration Management enabled] [https://jazz.net/jazz03/resource/itemName/com.ibm.team.workitem.WorkItem/98974] +-- Product Rational Team Concert Fixed in release 6.0.1: [APAR PI40247] [Source code data scanning not handling component replacement correctly] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/361670] [APAR PI42733] [Outplaced plan items at 4th level are not visible in Work Breakdown view] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/363579] [APAR PI43630] [Filter box and results view are not in sync] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/359913] [APAR PI43630] [Quick Planner Backlog shows resolved item] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/359928] [APAR SE62292] [genlink will fail by NPE when *SRVPGM that were created with EXPORT(*ALL)] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/362994] 7. 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.1: [APAR PI41290] [Source Code Data query of files found in All Streams but not in specific stream] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/361671] [APAR PI43630] [Improve debug tracing to help identify unsupported JREs] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/359630] [APAR PI43630] [NPE when proxy is specified] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/358964] 8. KNOWN ISSUES None.