Rational Team Concert for System z 2.0.0.1

Product Release / Trial | October 8, 2009
This is not the most recent version. We recommend Rational Team Concert for System z 2.0.0.2 interim fix 5. This is made available for archival purposes and may contain bugs and/or security vulnerabilities. If you do download this version, it is being provided AS IS, without warranties of any kind, including the implied warranties of merchantability and fitness for a particular purpose. We strongly advise you review the support pages for this version and update the product or take actions recommended therein. Security bulletins contain instructions for the security vulnerability addressed therein, and may require upgrading to a newer version. Link to security vulnerability blog: IBM PSIRT blog.

Getting Started
Featured Downloads
New & Noteworthy
Release Notes
All Downloads
Upgrading
Rational Team Concert for System z 2.0.0.1 Release Notes

The following notes detail issues in Rational Team Concert for System z 2.0.0.1 (October 8, 2009) that users and consumers of Rational Team Concert for System z should be aware of.

Detailed System Requirements

Consult the tech notes below for information about specific system requirements for Rational Team Concert for System z 2.0.0.1:

Program directories

See the tech notes below for copies of the Program Directories and special instructions required for installing and configuring Rational Team Concert for System z and WebSphere Application Server OEM Edition on z/OS:

Technical previews

See the tech notes below for copies of the Program Directories and special instructions required for installing and configuring Rational Team Concert for System z and WebSphere Application Server OEM Edition on z/OS:

Known issues

The following is a list of known issues and workarounds for the Rational Team Concert for System z v2.0.0.1 release:

Running the server under WAS OEM on z/OS

Issue Description:
When running the RTCz server under WAS OEM on z/OS you will notice a warning message on the Status Summary page of the RTCz server console with the text "CRJAZ1382E Unsupported Java virtual machine. Please upgrade to the latest version".
Workaround
We have tested the RTCz server functionality while running on this version of WAS OEM and found that the server is fully functional. The next release of WAS OEM will be packaged with Java 1.6 SR5 and this message will no longer be issued at this JVM level.

When lauching the RTCz server for the first time an exception can be logged

Issue Description:
On Websphere (z/OS or not), when first launching the server, you may find in the log this exception:
com.ibm.ws.webcontainer.servlet.ServletWrapper service SRVE0068E: Uncaught exception created in one of the service methods of the servlet equinoxbridgeservlet in application jazz_war. Exception created : javax.servlet.ServletException: org.apache.http.HttpException: Problem initializing theming namespace.

This will occur only for the first connection and has no consequences.
Workaround
None required.

Creating the server database using the Jazz Team Server setup from the Web UI will cause WAS for z/OS to terminate abruptly

Issue Description:
On Websphere for z/OS, you must create the server database using the repotools as documented. Using the Jazz Team Server setup from the Web UI to create the Jazz database tables will cause WAS to terminate abruptly.
Workaround
Use repotools to create the server database.

JCL build fails if RACF password is seven characters long

Issue Description:
A JCL driven build submitted through Rational Build Agent fails if the RACF password for JCL submission is seven characters long. When the build failed, the log shows the following error.
====
SUBMITJCL Job Monitor authorization failed with response "101 Usage error.%0A"
SUBMITJCL Unexpected return value from the job monitor, expecting "102"
Workaround
Use an eight character RACF password.

Mass Import tool imports files in UTF-8, but loaded files are in Cp1252 on IDE

Issue Description:
The mass import tool writes files into the repository in UTF-8; however, the default text file encoding in the RTCz Windows Eclipse client is Cp1252. If there are characters in the imported data set member that can be represented in UTF-8, but cannot be represented in Cp1252, users will see an error message when they make a change to the imported file in the RTCz Windows Eclipse client and try to save it.
Workaround:
Users of the Windows RTCz Eclipse-based client should configure their workspaces to use UTF-8 as the default text file encoding if they've used the mass import tool to import members from their data sets. They can do this by going to: Window -> Preferences -> General -> Workspace and changing the setting in the "Text file encoding" section to "UTF-8". Linux clients already use UTF-8 as the default text encoding. No change should be required for those using the Linux Eclipse-based client.

zFiles imported by Mass Import tool are not shown in RTC Web GUI

Issue Description:
The contents of zFiles created by the mass import tool are not viewable through the web UI. Attempting to open them in the web UI will result in the message "Unable to show file as its content is not text" being displayed instead of the contents.
Workaround:
Manually change the file's metadata in the RTCz Eclipse client:
  1. Load the repository workspace into your Eclipse workspace.
  2. Right click on the file and select "properties".
  3. In the "Jazz Source Control" page of the properties dialog, change the "Mime Type" field to "text/plain".
Check in the change from the pending changes view.

Round-trip code conversion is broken with zimport/loadz on SBCS undefined code points

Issue Description:
A COBOL source file can contain binary strings. If a binary string contains code points which do not have a valid UTF-8 character defined for it then the conversion process will convert those code points to the UTF-8 character U+FFFD (Replacement Character). If this source is then compiled during the Antz build process the source is transferred back to the host system and converted from UTF-8 back to EBCDIC. The UTF-8 to EBCDIC conversion will convert the U+FFFD character into X'6F' which is a question mark in EBCDIC. The original code points are not restored correctly and the round trip conversion of EBCDIC to UTF-8 to EBCDIC is broken in this situation.
Workaround:
None. Current limitation in this release.

Round-trip code conversion issues with zimport/loadz in special DBCS

Issue Description:
Source code that has been imported into the RTCz SCM using the Mass Import utility (zimport CLI command) and then compiled using the RTCz Antz build process can potentially contain code conversion errors when being converted from their original EBCDIC format to UTF-8 during the import and then from UTF-8 back to EBCDIC during the build process. This situation occurs when the source contains certain special DBCS characters such as 'X'FEFE' or X'0E0F'.
Workaround:
None. Current limitation in this release.

MalformedInputException thrown by zimport with ZLANG=IBM-939

Issue Description:
Source code containing certain special DBCS characters that have been imported into the RTC SCM using the Mass Import utility (zimport CLI command) will contain code conversion errors. If the environment variable ZLANG is used and set to the correct code page for the source then multiple MalformedInputException exceptions will be reported into the zimport logging. If the ZLANG environment variable is not used then the code conversion errors will still occur but silently.
Using mass import tool (zimport CLI command), during the conversion from z/OS EBCDIC characters into UTF-8 characters, some MalformedInputException can be raised even if the data set members are imported, as some special DBCS characters are not well converted.
Workaround:
None. Current limitation in this release.

zimport converts embedded X'0D', X'15' and X'25' into line breaks

Issue Description:
When a COBOL source file that contains any code points from X'00' to X'FF' in imbedded binary strings is imported using the zimport CLI command and loaded using the loadz CLI command, all code points except for X'0D' (EBCDIC carriage return) and X'15' (EBCDIC new line) are restored. Currently these code points will incorrectly get converted into a carriage return or new line.
Workaround:
None. Current limitation in this release.

Blank dataset prefix causes error when sharing members as zFiles

Issue Description:
If the Data Set Prefix attribute has not been set in a build definition and that build definition is used during the RDz integration Share or Load wizard operations the user will be presented with an error dialog containing the message "Data set could not be allocated due to a missing HLQ".
Workaround:
When selecting a build definition during the RDz integration Share or Load wizard operations make sure that the Data Set Prefix attribute has been set to a non empty value. If it is blank then edit this attribute and set it to an appropriate value. Both the Load and Share wizards have the capability of editing individual Build Definition attributes.

Content assist for Antz tasks does not prompt for attributes

Issue Description:
When you edit an Ant build script using Antz tasks/data sets, the content assist feature of the editor does not prompt for attributes of Antz tasks/data sets.
Workaround:
Input those attributes manually.

SYSPRINT output from High Level Assembler contains a few control codes

Issue Description:
Some host modules generate outputs with control characters on the first column. When RTCz Antz build code converts those outputs in UTF-8 encoding before publishing to RTCz server, some of control characters remain as garbage in the converted outputs.
Workaround:
None. Current limitation in this release.

Build request with java 1.5 64-bit version and the associated JVM

Issue Description:
When an Antz build is requested and a 64-bit Java Runtime Environment is used to start the Rational Build Agent on the System z platform, it fails with java.lang.UnsatisfiedLinkError.
Workaround:
RTCz currently only has support for the 31-bit version of native zOS library containing the functionality to invoke a compiler. Use a 31-bit Java Runtime Environment to start the Rational Build Agent on the System z platform.

Cannot specify a REXX exec for translator/language definition

Issue Description:
RTCz language definition can contain translators that are associated with an MVS module. If a REXX exec needs to be executed as a translator, there is no way to define a translator associated with it.
Workaround:
Instead of using Antz compile task, you can use Ant apply task to call a REXX script.
  1. Create a "dummy" translator called "REXX", which is associated with a nonexistent module.
  2. Create a "dummy" language definition called "REXX" and include the REXX translator.
  3. Associate zFiles with the REXX language definition.
  4. Write a shell script, which invokes a REXX script in a PDS(E) using the tso shell command. Following example invokes 'MYHLQ.JAZZ.EXEC(TEST)' with the parameters specified when the shell script is invoked.
    ====
#!/bin/sh                            
tso "EXEC 'MYHLQ.JAZZ.EXEC(TEST)' '${@}'" 
====
  5. Edit the build.xml file to add a target to invoke the shell script
    <!-- Process source files with a REXX exec.  -->
<target name="rexx" description="invoke rexx">
  <apply executable="/u/username/callrexx.sh" relative="true">
    <restrict>
      <antz:buildableset 
               buildableList="${teamz.scm.fetchDestination}/buildableFiles.xml"/>
      <antz:langdefselector name="REXX" caseSensitive="false"/>
    </restrict>
  </apply>
</target>

RTCz Translator cannot specify LIST option for z/OS C compiler with file name

Issue Description:
The LIST option of z/OS C/C++ compiler (see http://publib.boulder.ibm.com/infocenter/zos/v1r10/index.jsp?topic=/com.ibm.zos.r10.cbcux01/listcop.htm) can specify a file name as the listing output. This flexibility is not currently supported.
Workaround:
None. Current limitation in this release.

Antz build error with a Jazz user ID containing spaces

Issue Description:
If a Jazz user ID containing spaces is used for Antz build, it fails and a FileNotFoundException exception is reported.
Workaround:
Modify the startbfa.sh shell script and include double quotations with backslash characters in defining the JAZZ_USER environment variable. For example, if your Jazz user ID is "joe bob', define the JAZZ_USER environment variable like:
export JAZZ_USER="\"joe bob\""

Error when creating metadata for zFolders whose name contains special characters

Issue Description:
zFiles whose name contains special characters such as #, $, and @ can cause internal problems with the RTCz tooling. These characters are considered syntactic characters by the java URI specification. URIs are used for creation of the file level metadata.
Workaround:
Do not use special characters in zFile names.

Warnings in console following IM install on Solaris

Issue Description:
When you install the Jazz Team Server for System z on Solaris, AIX, or Linux for System z, you will see the warnings "WARNING [Thread:main] com.ibm.cic.common.core.repository.CompositeRepository getGroup." The warnings indicate that the repositories for ClearCase, ClearQuest, and the Rational Team Concert for System z client are not found. You can ignore these warnings because the offerings listed in the warnings are not supported on Solaris, AIX, and Linux for System z.

Load wizard fails to connect to repository server

Issue Description:
The Load zFiles to z/OS wizard issues an error if the user's repository connection URI does not match the Jazz server entry in the file agent's FileAgentConfiguration.dat.
Workaround:
Ensure that your repository connection is created with the same URI as is contained in FileAgentConfiguration.dat. This situation is commonly found when the client and the server are on the same machine and the user has specified 'localhost' as the repository URI. This situation can also occur when the client is connecting to a server from outside of a firewall with one URI but the File Agent running on the System z machine is behind the firewall and is connecting to the same server using a different URI. In all of these cases both the client and the File Agent must use the same URI to connect to the server.

Encoding mismatch issue in RDz when a project imported by Mass Import tool is used

Issue Description:
When the host System z machine is running certain code pages such as IBM-939, the Japanese EBCDIC code page and the RDz integration tooling is being used the following is possible. After loading zFiles from a repository workspace created by the Mass Import tool to an RDz MVS subproject using the "Load zFiles to z/OS" wizard, opening a member of the MVS subproject and closing it will cause a pending change to be shown, even if no change has been made.
Workaround:
Start the RSE client on z/OS with the UTF-8 encoding.

Merging a conflict causes an error message for RTCz/RDz integration scenario

Issue Description:
When working with zOS Project members that have been shared to RTCz, you should close all editors before accepting any incoming changes to files you are actively working with. Otherwise, the host member will be detected as locked and will be disconnected from the zFile. When this happens, you must run the Load zFiles to z/OS wizard to reconnect.
Workaround
Either close all editors before accepting any incoming changes or run the Load zFiles to z/OS wizard to reconnect.