December 4, 2017
IBM Rational Team Concert
Task tracking · Source control · Agile planning
Rational Team Concert 3.0.1
This release is a service release of Rational Team Concert version 3.0. It contains new features and fixes for defects. See the Getting Started tab for information on documentation and support resources; software and hardware requirements; installation or upgrade.
The following notes detail important fixes and issues in this release of Rational Team Concert. Please ensure that you also read the Jazz Foundation 3.0.1 Release Notes.
Fixes included in this release
The 3.0.1 release of Rational Team Concert delivers APAR and non-APAR defect fixes.
View the RTC development dashboard and the Collaborative Lifecycle Management development dashboard to review and explore completed work.
View the summary list of public APARs fixed for this release in the RTC APARs dashboard.
View the detailed list of public APARs fixed for this release using this query.
Known problems and workaroundsThe following are some of the known problems and workarounds in this release. To search for detailed support information for version 3.0.1, including known problems and workarounds, use the Rational Team Concert search and enter 3.0.1 in the Additional search terms field.
Build System Toolkit and Enterprise dependency build functionality on IBM i or z/OS
When the RTC server is upgraded to 3.0.1 you must also upgrade the Build System Toolkit that you are using on IBM i or z/OS to the 3.0.1 level as well. The v3.0 Build System Toolkit is not compatible with the v3.0.1 server when dependency based builds on IBM i or z/OS are being performed. Failure to upgrade the Build System Toolkit will result in all dependency based builds rebuilding every artifact each time a build is requested. Once the Build System Toolkit has been upgraded the first build performed will rebuild everything. Once this initial build has been completed all subsequent builds will only build what needs to be built.
DB2 on System z Data Warehouse Restriction
The reporting functionality in Jazz Team Server requires a data warehouse to operate. The data warehouse is a database which is configured as part of the server setup, and includes the following schemas: RIODS, RIDW, RICALM and CONFIG. A limitation in this release restricts DB2z users to a single data warehouse per DB2z subsystem, and hence effectively one JTS instance per subsystem. Installing multiple JTSs will require multiple DB2z subsystems.
DB2 for IBM i Data Warehouse Restriction
The reporting functionality in Jazz Team Server requires a data warehouse to operate. The data warehouse is a database which is configured as part of the server setup, and includes the following schemas: RIODS, RIDW, RICALM and CONFIG. A limitation in this release restricts DB2 for IBM i users to a single data warehouse per IBM i LPAR, and hence effectively one JTS instance per LPAR.
RDz Integration Version Feature Compatibility
RTC v3.0.1 includes an integration feature with the RDz product. This integration feature is compatible with RDz v8.0.1 to RDz v8.0.3
RDp Integration Feature Compatibility
RTC v3.0.1 includes an integration feature with the RDp product. This integration feature is compatible with RDp v8.0 (and any fix packs for RDp v8.0)
Error in documentation for setting up a DB2 database on z/OS
Under the topic : Installing > Installing the Rational solution for CLM > Setting up the database > Setting up a DB2 database on z/OS should be : "Because you are not using the same schema prefix you will be required to provide a new schema prefix in variable @newPrefix@"
Plan Editor and MyWork View don't render Chinese text on Eclipse 3.5.2. Eclipse defect prevents Chinese text from being rendered in the Planned Items tab. More details and workaround are documented in Team Concert defect.
Files in IBM-1047 encoding cannot be shared with Jazz SCM using IBM 1.5 VM. Click here to see more information.
Team Concert Client for Visual Studio
Users will not be able to create or associate non-Jazz based OSLC artifacts to Team Concert changeset or link to a work item using Team Concert Client for Visual Studio. Please use the Team Concert Eclipse or Web client for these operations. See 168052 for details.
Help preferences when upgrading Team Concert client for Eclipse IDE and Team Concert client for Microsoft Visual Studio IDE
If you encounter problems accessing the 3.0.1 help from within the Rational Team Concert client for Eclipse IDE or the Rational Team Concert client for Microsoft Visual Studio IDE after you upgrade one of those clients, ensure that your help preferences are set correctly:
- In the client, click Window > Preferences.
- Expand the Help entry and click Content.
- Ensure that the URL for the Rational Team Concert entry is http://publib.boulder.ibm.com/infocenter/clmhelp/v3r0m1 and that it is Enabled. If there is a second entry for Rational Team Concert, which specifies the 3.0 URL (http://publib.boulder.ibm.com/infocenter/clmhelp/v3r0), disable or remove that entry