IBM Support

Rational Quality Manager Interim Fix 6 for 5.0.2

Download


Abstract

IBM Rational Quality Manager 5.0.2_iFix006 has been made generally available and contains fixes to version 5.0.2 including all predecessor fixes.

Download Description

Table of Contents
Sections Description

The Change history section provides an overview on what is new in this interim fix with a description of any new functions or enhancements when applicable.

The How critical is this fix section provides information related to the impact of this interim fix to allow you to assess how your environment may be affected.

The Prerequisites section provides important information to review prior to the installation of this interim fix.

The Download package section provides the direct link to obtain the download package for installation in your environment.

The Installation instructions section provides the installation instructions necessary to apply this interim fix into your environment.

Click to review a complete list of the defects (APARs) resolved in this interim fix.

The Known side effects section contains a link to the known problems (open defects) identified at the time of this interim fix.
Supporting Documentation
Document Description

Click to review the detailed system requirements information for a complete list of hardware requirements, supported operating systems, prerequisites and optional supported software, with component-level details and operating system restrictions.

IBM Knowledge Center provides an entry point to product documentation. You can view, browse, and search online information related to the product.

The Jazz initiative consists of three elements: Platform, Products and Community. Explore the jazz.net product page.

Find technical developer content and resources.

Prerequisites

Prerequisites include:

IBM Rational Quality Manager 5.0.2 must be installed to apply this iFix.

Note: Before you install the server patch file, verify that no other test fixes are installed. If other fixes are installed, contact IBM Software Support.

Back to top

Installation Instructions

Tab navigation

Note: Before you install this server patch file, 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.

Procedure to install the server patch:

  1. Stop the CLM server.

  2. Verify whether the following directory exists: server_installation_directory/server/patch.
    • If the directory exists, back up and remove its contents.
    • If the directory does not exist, create it.

  3. Copy the server patch file into the /server/patch directory.

  4. Start the server.

Note: For a distributed CLM deployment, complete the same steps on each server.

Procedure to uninstall the server patch:

  1. Stop the CLM server.

  2. Back up and remove the contents of the following directory: server_installation_directory/server/patch

  3. Start the CLM server.

Note: For a distributed CLM deployment, complete the same steps on each server.

Procedure to install the Data Collection Component patch:

  1. Stop the DCC server.

  2. Verify whether the following directory exists: server_installation_directory/server/patch.

  3. If the directory exists, back up and remove its contents.

  4. If the directory does not exist, create it.

  5. Copy the server patch file into the /server/patch directory.

  6. Start the DCC server.

Procedure to uninstall the Data Collection Component patch:

  1. Stop the DCC server.

  2. Back up and remove the contents of the following directory: server_installation_directory/server/patch

  3. Start the DCC server.

Procedure to install the patch with JRS deployed on Apache Tomcat server:

  1. Stop the JRS Tomcat server

  2. Copy the following file to a backup directory in the event you need to revert the patch:
    • JRS_Install\server\tomcat\webapps\rs.war

  3. Delete the following file:
    • JRS_Install\server\tomcat\webapps\rs.war

  4. Delete the following directories:
    • JRS_Install\server\tomcat\webapps\rs
    • JRS_Install\server\tomcat\work\Catalina\localhost\rs

  5. Place the new rs.war file under JRS_Install\server\tomcat\webapps

  6. Start the server

Procedure to uninstall the patch with JRS deployed on Apache Tomcat server:

  1. Stop the JRS Tomcat server
  2. Restore the original rs.war that was backed up in step 2 of the install instructions to the following directory
    • JRS_Install\server\tomcat\webapps\
  3. Delete the following directories:
    • JRS_Install\server\tomcat\webapps\rs
    • JRS_Install\server\tomcat\work\Catalina\localhost\rs
  4. Start the server

Procedure to install the patch with JRS deployed on WebSphere Application Server:

  1. Unzip the reporting-war zip file somewhere either on your local machine or on the JRS server.

  2. In the WAS Admin Console, stop the JRS application: Go to Applications > Application Types > Websphere enterprise applications, select the checkbox next to rs_war and click on Stop.

  3. Update the rs_war file: Select the checkbox next to rs_war and click on Update.

  4. Select "Replace the entire application", then browse to the new rs.war file from the unzipped directory and click on Next. Browse locally if the file was saved on the local machine in step 1, or do a remote browse if the file was saved on the JRS server. Follow the Fast Path installation, and accept all of the defaults.

  5. Save the configuration changes when prompted after the update completes.

  6. Start the JRS application: select the checkbox next to rs_war and click on Start.

Procedure to uninstall the patch with JRS deployed on WebSphere Application Server:

  1. Locate the rs.war file in the original JRS installation.

  2. In the WAS Admin Console, stop the JRS application: Go to Applications > Application Types > Websphere enterprise applications, select the checkbox next to rs_war and click on Stop.

  3. Update the rs_war file: Select the checkbox next to rs_war and click on Update.

  4. Select "Replace the entire application", then browse to the rs.war file in the original JRS installation and click on Next. Browse locally if the file was saved on the local machine in step 1, or do a remote browse if the file was saved on the JRS server. Follow the Fast Path installation, and accept all of the defaults.

  5. Save the configuration changes when prompted after the update completes.

  6. Start the JRS application: select the checkbox next to rs_war and click on Start.

Back to top

Download Package

The following sections provide detailed information related to this interim fix.

Click the FC link below to obtain the interim fix from Fix Central.


How critical is this fix?

Impact Assessment
Impact Description

Corrective

This is a maintenance interim fix. It contains fixes for client-reported and internally found defects.

Test Results

Close [x]

Definitions

Regression: An error in the Maintenance Delivery Vehicle (MDV) that produces incorrect or unexpected behavior causing a supported feature to stop functioning as designed.
This includes:

  • Coding errors that cause a regression
  • Documentation or packaging problems that cause a regression
  • Errors reported in a new function delivered in a MDV that cause a regression

Incomplete: An error in the MDV has not regressed, but does not work as designed.
This includes:

  • Fixed APARs which did not solve the original problem but did not break anything new
  • APARs reporting documentation errors, such as readme errors, that cause problems applying an MDV but do not lead to a regression

Notes:
  • Regression and incomplete APARs are considered fix-in-error or MDV-in-error
  • Definitions above apply only to valid APARs that result in product fixes (APARs returned as working-as-designed are not assessed for being fix-in-error)
  • Issues in major releases due to new functionality do not apply in this definition

There are no known regressions to report.

PSIRT Blog

 In addition to the fixes listed in this document, the iFix may also contain fixes for security issues.

For more details, please refer to the IBM Product Security Incident Response (PSIRT) Blog.

Back to top

Problems Solved

Defects resolved in this iFix.

This server patch contains fixes for the following defects:
APAR (WorkItem URL) Description
Rational Data Collection Component
PI28909

[Backport 5.0.2] Dashboard report is showing the last time the Java ETLs were run not when the last DCC ETLs were run.

PI29074

[Backport 5.0.2] CQPAR00108139: Job status shows failure for all resource groups even though only one of them actually failed.

PI30420

[Backport 5.0.2] [DCC] Records marked as softdeleted in TIMESHEET could be active again - DCC.

PI39043

[Backport 5.0.2] DCC - Timesheet ETL issues.

PI40747

[Backport 5.0.2] DCC open file descriptor Leaks behavior.

PI40912

[Backport 5.0.2] DCC: ODS Collector jobs are in waiting state forever if there was a temporary DB connection problem.

Jazz Reporting Service
PI31540

[Backport 5.0.2] JRS data source issues when using LDAP and custom DW extension names that end with “.‿.

PI33336

[Backport 5.0.2] CQPAR00118878: Custom Enumerations in certain case display as literal ID instead of name.

PI33321

[Backport 5.0.2] CQPAR00118829: JRS Not able to Handle RQM Categories like Attributes.

PI28909

[Backport 5.0.2] Missing custom link types for requirements.

PI36076

[Backport 5.0.2] Issues with RM custom attributes.

PI28909

[Backport 5.0.2] Able to download query spreadsheet non-authenticated/authorized, potential for malicious use and phishing attack.

PI28909

[Backport 5.0.2] JRS using the data warehouse is showing no results in non CM-enabled project traceability reports from requirements.

PI36678

[Backport 5.0.2] DW data source SQL queries do not handle a schema prefix.

PI37951

[Backport 5.0.2] Report Builder lists Soft Deleted project areas when selecting Scope.

PI28909

[Backport 5.0.2] JRS Failing to Input Validate and output encode data, leading to potential XSS (Cross Site Scripting) Vulnerability.

PI38981

[Backport 5.0.2] Project List Excludes Project Areas that do not have team areas.

PI41444

[Backport 5.0.2] Metamodel initialization should happen on server startup.

PI22400

Fix defect in redirect web page.

PI28909

Use TLS instead of SSL by default.

PI31655

The LPA templates can not be retrieved after a migration from 5.0.1 (with a server rename) to 5.0.2.

PI33587

LocalGroupLDAP doesn't support case insensitive mode (343625) [5.0.2].

PI33689

All Project Areas are deleted during upgrade to RDNG 5.0.2 if finalizeApplicationMigration is rerun following a failure.

PI36961

Full Text Search stemming doesn't work correctly in non-English European languages (Backport 345158 to 5.0.2 ).

PI41256

RRC Project Baselines are inaccessible after migration from 4.0.x in a server renamed environment.

Rational Jazz Foundation
PI28526

NPE in ManagedFloatingLicenseClient$LeaseCache.getCheckoutOperations.

PI28909

Adding new roles in Web UI makes it VERY easy to seriously corrupt roles database - Chrome only.

PI28909

Diagnostics Oracle JDBC Driver version check does not accept 12.1.0.2.

PI28909

Error during creation of Life Cycle Project in CLM 5.0.2RC1 with JazzProjectAdmins permission.

PI28909

Investigate implications of two components having the same ID.

PI28909

Issue #1 Maintenance 5.0.2 - PMC 341917.

PI28909

Issue #3 Maintenance 5.0.2 - PMC 341970.

PI30407

RTC ETL's should be able to handle date values where the year is not 4 digits long.

PI30488

DelegatedAuthHandler and LoginPageStatusHandler ignores com.ibm.team.jfs.app.oauth.OAuthHelper.disableSecureCookies property.

PI31126

The iteration type should not be restored if it's not archived.

PI31655

The LPA templates can not be retrieved after a migration from 5.0.1 (with a server rename) to 5.0.2.

PI31729

5.x Indexer for Excel can run out of memory.

PI33689

All Project Areas are deleted during upgrade to RDNG 5.0.2 if finalizeApplicationMigration is rerun following a failure.

PI34460

Adopt Report caching slow on Oracle (344963).

PI36337

Project Dashboard shows incorrect content after loading a WI or Query Result and then performing a browser refresh in IE.

PI36961

Full Text Search stemming doesn't work correctly in non-English European languages (Backport 345158 to 5.0.2 ).

PI37026

Online Migration can skip states in the event of a retry-able DB exception (fix in 5.0.2).

PI37053

Creating iterations can break if translation is wrong (Fix in 5.0.2).

PI37117

Handle the query cancellation in query iterator and QueryFilter (resource context filter).

PI37679

Query Results from performQuery can be unexpectedly cached (Backport 348143 to 502ifix ).

PI37709

Online migration can skip states on subsequent runs.

PI38110

Deleting resource in no-history storage area should not update history index to 502 (Backport 351405 to 502).

PI40009

Lucene crashes because of Mmap issue (Backport to 502).

PI40126

TeamAreaRole ETL flips two columns (354920).

PI40589

[RTC 5.0.2] [wi 356278] - ETL should ignore Item not found exceptions.

PI41256

RRC Project Baselines are inaccessible after migration from 4.0.x in a server renamed environment.

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

Rational Quality Manager
PI27350

Shared Queries added to the menu list will not run in the artifact Table View, if a filter attribute was updated just before attempting to run the shared query.

PI28778

QM Japanese character corruption in file name after run offline in RQM.

PI28798

Test Suite Log Put handler changes the execution request and task result of the test suite result.

PI28859

Requirement back link is not deleted when deleting a test case deleted.

PI28909

502M: QMI pipeline of build CALM502M-I20150507-0242 failed.

PI28909

After generating testcases from requirements using reconcile, some test cases' titles are shown as their respective URLs.

PI28909

An error occurred during validation of the RM project when migrating the links from Reqpro to RDNG.

PI28909

ClassCastException when reconciling requirements.

PI28909

Missing summary when reconciling requirement collections with new requirements.

PI28909

Print PDF fails (Summary and Comprehensive) from a Test Test suite.

PI28909

Service dependency errors in full text indexing at startup.

PI28909

Test Plan cannot be opened after upgrade to 5.0.2.

PI29010

RQM Test Plans->Requirement Section->Rational RequisitePro tab (no option to sort ascending/descending by any of the columns).

PI29222

HiddenMenusWebUIInitializer loads data for all projects causing performance issues with many PAs.

PI29782

QM : Unable to save a test script that contains two steps with the same keyword.

PI29860

Generate TCER wizard keeps resizing and recentering itself causing the buttons to change location making it frustrating to use.

PI29865

QM: Unexpected behavior when deleting category values.

PI30175

Precondition "Disallow Saving of Test Plans with State Approved" does not prevent a Formal Approval Group from being deleted and saved.

PI30267

QM : Duplicating Test Scripts across project areas including Keywords.

PI30404

Validate date for RQM Reportable REST API when etlmode=true.

PI30600

java.lang.IllegalArgumentException: Item Handle array cannot exceed 2048 elements during QM phase to iteration migration.

PI30764

Links new requirement to test case under coverage view,it shows as updated status in the Reconcile Requirement window.

PI30797

NI TestStand Adapter registers the incorrect IP address and MAC address with the RQM server due to RQM incorrectly matching existing ip addresses in a DHCP environment.

PI30849

The "Wrap words to show all" cell text display option in the Requirement Links section is not sticky.

PI32571

Resource Group Names in XDC file should be truncated only if needed.

PI32578

OslcQmService.service hangs while hovering on Test Script link when Test Script uses Archived Test Data.

PI33024

QM : Image Verification Points (RFT Test Script) are not present in the result PDF file output.

PI33515

QM: Test Suite Execution behavior difference between version 4x and 5x.

PI33606

Irrelevant TCERs for a TSER.

PI33740

QM: Page refresh on an execution schedule page report that unsaved changes exist [Contains Unsaved Changes] and the Save/Cancel button is enabled.

PI34626

RQM API cannot query for iteration that has been renamed.

PI34659

The "Test Case Results" section of Test Plan Snapshot does not contain the test case results - the data is missing.

PI34877

QM: TER creation does not get latest version of test script if the recent change in the test script is a keyword removal.

PI34972

Multiple test script links are referencing to a keyword.

PI36406

QM Micro Execution Status by Owner user TCER Count writing errors in the log.

PI36575

Table view column content is not resized automatically when window is resized.

PI36669

comprehensive PDF of test plan includes some artifacts not related to test plan.

PI36891

Opening <Test case Result> page using copied URL does not work.

PI36950

Users without JazzProjectAdmins repository permission have to reload the artifact to see the new category value created.

PI37461

Back out dashboard auto-refresh interval of 5 minutes - Backport for 5.0.2.

PI37539

Manual test script steps/results with rich text containing upper ASCII characters are corrupted on refresh when the server is renamed.

PI37937

You can't change iteration on an executed test suite when start execution from inside of a test plan.

PI37940

Do Apply All on a test script step and you loose added information on that step.

PI37941

Adding Executing Variable to a test script step with Swedish characters makes all with dots above them shows as ?.

PI38112

Need explicit purge support for ExecutionElement2 summary.

PI38306

Unable to save query (Test Case Execution Records query) by owner.

PI38754

updating custom sections via a PUT has no effect.

PI38785

QM Test Environment and Platform Coverage sections do not show in a snapshot.

PI38792

No Maximize button on the Results Details section of a TER for scriptless execution results.

PI39117

Test script not included in test case section of Test Suite comprehensive PDF export.

PI39446

To show IDs in RQM backlinks in CQ link tab.

PI39506

Improve the performance of the QM - DNG Reconcile operation.

PI40575

The Test Category can not Restored from Trash View when any of its Value has been Permanently Deleted.

PI40610

RQM Default Reports: Execution States which were renamed are not matching with reporting columns.

PI41025

Cannot Delete Test Asset if Auto-Assign Ownership to Creator Follow-up Action Applied.

PI28909

RQM Reportable REST API JUnit failures.

PI28909

testBulkUpload() failed.

PI41222

QM ETL Failures related to executionscriptstep artifact.
Additional fixes:
APAR (WorkItem URL) Description Steps to apply
Rational Jazz Foundation
PI22400

Fix defect in redirect web page.

NOTE: If the context root used by the any application is not the default, it will be necessary to rename the WAR file (and adjust some of the directory paths referenced below) based on the context root currently in use. For example,

  • if your current context root for Requirements Management is 'rdm', you must rename the rm.war file to rdm.war.
  • if your current context root for Quality Management is 'jazz', you must rename the qm.war file to jazz.war
  • if your current context root for Change and Configuration Management is 'jazz', you must rename the ccm.war file to jazz.war

In summary, the name of the WAR file needs to be the same as the respective context root in use.

NOTE: For users of the RDNG browser add-on, the rm.war file must be properly matched with the browser plugin files. This only applies during installation of the plugin, so for those users that have already installed the plugin, no action is required. For any new installations of the browser plugin, the customer should contact IBM Support and request a refresh of the browser add-on files along with the properly paired version of the rm.war file that includes this fix.

DEPLOYING ON WEBSPHERE APPLICATION SERVER

  1. Backup these files:
    1. JAZZ_HOME/server/webapps/jts.war
    2. JAZZ_HOME/server/webapps/ccm.war
    3. JAZZ_HOME/server/webapps/qm.war
    4. JAZZ_HOME/server/webapps/rm.war
  2. Copy the jts.war file somewhere either on your local machine or on the CLM server (you may copy to the JAZZ_HOME/server/webapps directory)
  3. In the WAS Admin Console, stop the jts application: Go to Applications>Application Types>Websphere enterprise applications, select the checkbox next to jts_war and click on Stop.
  4. Update the jts_war file: Select the checkbox next to jts_war and click on Update.
  5. Select "Replace the entire application", then browse to the new jts.war file from step 2 and click on Next. Browse locally if the file was saved on the local machine in step 1, or do a remote browse if the file was saved on a different machine. Follow the Fast Path installation, and accept all of the defaults.
  6. Save the configuration changes when prompted after the update completes.
  7. Start the jts application: select the checkbox next to jts_war and click on Start.
  8. Repeat 2-7 with all other WAR files that you need to upgrade.

DEPLOYING ON TOMCAT

  1. Backup these files:
    1. JAZZ_HOME/server/tomcat/webapps/jts.war
    2. JAZZ_HOME/server/tomcat/webapps/ccm.war
    3. JAZZ_HOME/server/tomcat/webapps/qm.war
    4. JAZZ_HOME/server/tomcat/webapps/rm.war
  2. Copy the WAR files to the JAZZ_HOME/server/tomcat/webapps directory.
  3. Stop the Tomcat server.
  4. Delete the JAZZ_HOME/server/tomcat/webapps/jts directory.
  5. Delete the JAZZ_HOME/server/tomcat/webapps/ccm directory.
  6. Delete the JAZZ_HOME/server/tomcat/webapps/qm directory.
  7. Delete the JAZZ_HOME/server/tomcat/webapps/rm directory.
  8. Delete the JAZZ_HOME/server/tomcat/work/Catalina/localhost/jts directory.
  9. Delete the JAZZ_HOME/server/tomcat/work/Catalina/localhost/ccm directory.
  10. Delete the JAZZ_HOME/server/tomcat/work/Catalina/localhost/qm directory.
  11. Delete the JAZZ_HOME/server/tomcat/work/Catalina/localhost/rm directory.
PI28909

Use TLS instead of SSL by default.
  1. Stop the Apache Tomcat server.
  2. Back up the JAZZ_HOME/tomcat/conf/server.xml file to server.xml.bak.
  3. Extract the ServerConfigrurationToUseTLSFor407iFix004.zip file to a temporary directory.
  4. Copy the server.xml file to the JAZZ_HOME/tomcat/conf directory.
  5. If you made any custom configuration changes to your server (such as changing port numbers), manually copy them from server.xml.bak to the new server.xml file.
  6. If you are using Windows:
    1. Back up the JAZZ_HOME/server/server.startup.bat file to server.startup.bat.bak.
    2. Copy the server.startup.bat file to the JAZZ_HOME/server/ directory.
    3. If you made any customizations to the server startup file, manually copy them from server.startup.bat.bak to server.startup.bat
  7. If you are using Linux:
    1. Back up the JAZZ_HOME/server/server.startup file to server.startup.bak.
    2. Copy the server.startup file to the JAZZ_HOME/server/ directory.
    3. If you made any customizations to the server startup file, manually copy them from server.startup.bak to server.startup
  8. Start the server
PI31655

The LPA templates can not be retrieved after a migration from 5.0.1 (with a server rename) to 5.0.2.
  1. Go to the JAZZ_HOME/server directory.
  2. Execute the following command: 
    repotools-jts -clean
PI33587

[5.0.2] LocalGroupLDAP doesn't support case insensitive mode (343625).

This change is only relevant if you need to use LocalGroupLDAP in case insensitive mode.

  1. Stop the Apache Tomcat server
  2. Rename JAZZ_HOME/server/tomcat/lib/com.ibm.team.repository.localgroups.realm_1.1.2100.v20140602_2352.jar to JAZZ_HOME/server/tomcat/lib/com.ibm.team.repository.localgroups.realm_1.1.2100.v20140602_2352.jar.orig
  3. Copy the attached plugin com.ibm.team.repository.localgroups.realm_1.1.2100.v20150214_0216.jar into the JAZZ_HOME/server/tomcat/lib
  4. Add the line 
    ignorecase="true"
    as below to tomcat/conf/server.xml: 
    Resource name="LocalRoleMap" auth="Container"
			type="com.ibm.team.repository.localgroups.IUserRoleMap"
			descripion="Role mapping file"
			factory="com.ibm.team.repository.localgroups.realm.RoleMappingResourceFactory"
			ignorecase="true"
			pathname="/opt/jazz/server/mapping.csv" />
  5. Start the Apache Tomcat server
PI33689

All Project Areas are deleted during upgrade to RDNG 5.0.2 if finalizeApplicationMigration is rerun following a failure.
  1. Go to the JAZZ_HOME/server directory.
  2. Execute the following command: 
    repotools-jts -clean
PI36961

Full Text Search stemming doesn't work correctly in non-English European languages (Backport 345158 to 5.0.2 ).

Language specific stemming is not enabled by default. To enable specific language stemming, select the Advanced property page of each application (e.g. ccm, qm, jts...). Change the value of 

com.ibm.team.fulltext.lucene.language.stemmer.enabled
to 
true
.

Restart the server.

The setting has three values:

  1. "legacy" (the default) for compatibility with the existing indices. In this case the English stemmer is used for all languages (except for the Asian languages).
  2. "true" which enables a stemmer specific to the language defined by the "Indexing Language" property or by the server locale if the property is not set.
  3. "false" which disables stemming all together

Note, if you've already created workitems in a non-English European language, you need to run repotools -rebuildTextIndices to be able to search these with language-specific stemming.

The stemmer uses the default language specified on the server machine.

Back to top

Known Side Effects

The following defects were not resolved in this interim fix:

Review the 5.0.2 Release Notes page on jazz.net for links to queries that list known problems and workaround articles for this release.

Open defects

Review the following list of open APARs for Rational Quality Manager on the IBM Support Portal.

Review technote 1461170: Open APARs for Rational products available on the Web for information on how to configure your MyNotifications subscription account and subscribe to the APARs you are interested in following.

Back to top

Change History

What's new

No new features or functions in this iFix.

Review the 5.0.2 New and Noteworthy page on jazz.net for a description of the new features included in this release.

Back to top

Click the link in the Download Options column:

On
[{"DNLabel":"RQM 5.0.2 iFix_006","DNDate":"3 Jun 2015","DNLang":"English","DNSize":"274854461","DNPlat":{"label":"Windows","code":"PF033"},"DNURL":"http://www.ibm.com/support/fixcentral/swg/quickorder?parent=ibm%7ERational&product=ibm%2FRational%2FRational+Quality+Manager&release=5.0.2&platform=All&function=fixId&fixids=5.0.2-Rational-RQM-ifix006&includeSupersedes=0&source=fc","DNURL_FTP":" ","DDURL":null}]

Technical Support



Tab navigation











IBM Rational Software Support Communities


  • Visit the IBM Support Portal to configure your support portal experience and review FAQs, lists of known problems, fixes, and a wealth of important support information.


  • Visit developerWorks to access an online collection of tutorials, sample code, standards, forums and other resources provided by experts at IBM to assist software developers using Rational tools including access to the IBM RFE Community.


  • Visit the Jazz Community if you use a Rational product created using the Jazz platform to interact directly with the Jazz development team and other community members, download product trials and betas and track development progress.


Helpful Hints For Obtaining Technical Assistance:


Before you contact IBM Rational Software Support, gather the background information that you need to describe the problem. When you describe a problem to an IBM software support specialist, be as specific as possible and include all relevant background information so that the specialist can help you solve the problem efficiently. To save time, know the answers to these questions:


  • What software versions were you running when the problem occurred?
  • Do you have logs, traces, or messages that are related to the problem?
  • Can you reproduce the problem? If so, what steps do you take to reproduce it?
  • Is there a workaround for the problem? If so, be prepared to describe the workaround.

If you have helpful information to diagnose or identify the problem on your system, you can provide this data by following the instructions to exchange information with IBM Technical Support.


Follow IBM Rational Client Support on Twitter | Facebook | YouTube | devWorks Blog







Back to top

[{"Product":{"code":"SSUVV6","label":"IBM Engineering Test Management"},"Business Unit":{"code":"BU055","label":"Cognitive Applications"},"Component":"Installation","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"5.0.2","Edition":"","Line of Business":{"code":"LOB02","label":"AI Applications"}}]

Product Synonym

Rational Quality Manager

Problems (APARS) fixed
PI31540;PI33336;PI33321;PI36076;PI36678;PI37951;PI38981;PI41444;PI33587;PI22400;PI40912;PI40747;PI39043;PI30420;PI29074;PI28526;PI28909;PI30407;PI30488;PI31126;PI31655;PI31729;PI33689;PI34460;PI36337;PI36961;PI37026;PI37053;PI37117;PI37679;PI37709;PI38110;PI40009;PI40126;PI40589;PI41256;PI41335;PI27350;PI28778;PI28798;PI28859;PI29010;PI29222;PI29782;PI29860;PI29865;PI30175;PI30267;PI30404;PI30600;PI30764;PI30797;PI30849;PI32571;PI32578;PI33024;PI33515;PI33606;PI33740;PI34626;PI34659;PI34877;PI34972;PI36406;PI36575;PI36669;PI36891;PI36950;PI37461;PI37539;PI37937;PI37940;PI37941;PI38112;PI38306;PI38754;PI38785;PI38792;PI39117;PI39446;PI39506;PI40575;PI40610;PI41025;PI41222

Document Information

Modified date:
20 July 2018

UID

swg24040167

Page Feedback