Release notes: Version 20.13.01 of BMC Compuware Topaz Workbench

Topaz Workbench

CLI installation location

If upgrading from a release prior to 19.05, for Windows installations the Topaz Workbench CLI, the default install path location has been changed to C:\Topaz\WorkbenchCLI to better address access issues caused by the previous default path of C:\Program Files\Compuware\Topaz Workbench CLI. The new default is specified in the install wizard and can be changed during installation.

Eclipse memory settings

Java OutOfMemory errors may occur when editing a large file or displaying a large JES report. These errors can often be avoided by increasing the maximum size of the JVM memory heap. The initialization files in Topaz Workbench or Eclipse (topaz.ini or eclipse.ini) include an Xmx parameter (Eclipse default 1024m or Topaz default 2048m) used to specify the maximum heap size. The optimum value for this parameter varies depending on the OS used, memory fragmentation, and other factors.

The optimal setting for a particular installation—with no OutOfMemory errors or noticeable garbage collection pauses—can only be determined by experimenting with different values. We recommend increasing the Xmx value to 1200m as a starting point and increasing or decreasing the value in small increments, such as 512m, until an optimum value is found. However, even with a setting of 1536m, large JES output can easily exceed that value.

On 64-bit Windows operating systems, heap size is limited by your Windows virtual memory specification, minus a small amount of memory used by the OS and other processes. Specifying 4-GB or more for the Xmx parameter might be practical, depending on the Windows virtual memory size.

eGit compatibility

eGit versions 4.6.1 through 5.0.1, 5.04, and 5.13 are compatible with Topaz Workbench releases with major version 20. eGit versions 5.02 and 5.03, however, exhibit known issues with the eGit UI and are not compatible with Topaz Workbench releases.

Fault Analytics EOS

Fault Analytics has stated End of Support from July 1, 2020. Beginning October 2020, Fault Analytics is no longer installable through Topaz Workbench.

Host Explorer licensing

Use of Host Explorer requires a valid Compuware Mainframe License (any product) on any LPAR serving Host Explorer connections. The HCI hosting these communications must have access to Compuware’s License Manager.

If there is any licensed Compuware mainframe product running on an LPAR where HCI is executing, no further effort is necessary.

IBM IDz support

Topaz Workbench release 20.05.03 and later are supported for installation into IBM Developer for z Systems (IDz) 15.0.1, 15.0.4, and 15.0.5 releases. To use this support, enable Java Development Tools (JDT) and Debug Support. Select Windows > Preferences > General > Capabilities > Development , and then check the boxes to enable Debug Support and Java Development .

Running Topaz Workbench in 32-bit mode on a 64-bit OS

Topaz Workbench 20.xx releases no longer support running on Windows 32-bit versions or in 32-bit mode.

VIPA networks

A minimum of HCI 3.0 is required for VIPA networks.

Compuware Shared Services enhanced listings

Connection to LPAR

Xpediter/Eclipse requires a direct connection to an LPAR with a working version of Xpediter/CICS, Xpediter/TSO, or Xpediter/IMS on any LPAR where Xpediter debugging sessions are to execute.

Topaz Enterprise Data

Audit preference

By default, the Enable Auditing preference is turned on and an audit file is created on the mainframe. Be aware that when auditing is enabled, the FORCE option on the Concurrent Update view does not work because it would negate the audit.

Database connection for Compuware DB2 for z/OS

After installing the Compuware DB2 for z/OS using Topaz (base) feature, a database connection must be established. From the New Connection Profile option in the Data Management - Data Source Explorer view, under Database Connections - New, select DB2 for z/OS using Topaz.

Eclipse-based IDE installs

You must include and enable the following update sites:

• For Photon:
  • http://download.eclipse.org/releases/photon
  • http://download.eclipse.org/eclipse/updates/4.8
• For higher Eclipse releases, use the equivalent level download sites.

License checking requirements

• Compuware Enterprise Services (CES) 19.05.01 or later is required, and Topaz Enterprise Data components must be configured to identify CES location.
• If you intend to access mainframe data, apply Enterprise Common Components (ECC) PTF CXS905A. This PTF returns a list of File-AID licenses to CES.

Oracle 19c support

Users upgrading Topaz Workbench from versions earlier than 20.03 via P2 upgrades might need to upgrade from ojdbc6.jar to ojdbc8.jar. The xdb6.jar has also been updated. Both jars are in the <topaz-install-location>\drivers\folder.

Topaz Workbench Datatools

If you intend to use Topaz Workbench Datatools, install only the Compuware DB2 for z/OS using Topaz (base) feature. This plug-in is not required if the native Eclipse datatools plug-ins will be utilized.

Topaz for Total Test

Generating unit test cases for very large programs

Generating Topaz for Total Test unit test cases for very large programs might require increasing the memory allocated to Topaz Workbench. To do this, edit the topaz.ini file in your installation directory of Topaz Workbench (the default path is C:\Users\userid\Compuware\Topaz\eclipse).

Find the entry -Xms256m and change it to -Xms512m.

This adjustment doubles the amount of memory available to the Topaz Workbench and Topaz for Total Test. Save the topaz.ini file and restart Topaz Workbench.

Java Runtime Environment (JRE)

A 64-bit JRE is required for the Topaz for Total Test Command Line Interface (CLI).

KSDS support

Topaz for Total Test does not support KSDS READ NEXT using an alternate key for which duplicates are allowed when there are duplicates and they are not ordered in prime key order.

Pipeline Syntax

The junit and sonar files have been renamed as follows:

• -f "MyProject/MyTests/SimpleTest/Unit Test/Scenarios"
  The junit is now Scenarios.cli.suite.junit.xml.
  The sonar is now Scenarios.cli.suite.sonar.xml.
  The TTTJUNIT and TTTSONAR directories are now located in the Unit Test directory.
• -f “MyProject/MyTests/SimpleTest/”
  The junit is now SimpleTest.cli.suite.junit.xml.
  The sonar is now SimpleTest.cli.suite.sonar.xml.
  The TTTJUNIT and TTTSONAR directories are now located in the SimpleTest directory.

The junit and sonar files always have the last directory specified on the -f option in the name examples.

Xpediter/Eclipse

Compuware Shared Services enhanced listings

Connection to LPAR

Xpediter/Eclipse requires a direct connection to an LPAR with a working version of Xpediter/CICS, Xpediter/TSO, or Xpediter/IMS on any LPAR where Xpediter debugging sessions are to execute.

Topaz Workbench

We have added conditions for the backspace and delete in COBOLFixedFormatEventHandler and also check the length of the line while update the tags.

Able to delete all of the lines in a COBOL program using Ctrl-A and the ‘Del’ key in large files also.

We have fixed the cut operation in COBOL editor so that it does not delete the tags when any part of the line is cut.

We have resolved the extraneous input and mismatched input errors in the COBOL PG0GX192 program.

We have added support for "¦' character in the PL/I parser as OR and CONCATENATION character for all nine combinations of (!, |, ¦) to accommodate the different keyboard layouts (CH/DE/IN/UK etc.).

Topaz Enterprise Data

We have fixed an issue where the ConverterPro does not update Clob type field when the source is set to null.

In File-AID for DB2 Editor, the ClassCastException error for DB2RecordStore is now fixed.

In File-AID for IMS Editor, the ClassCastException error for IMSRecordStore is now fixed.

The fix is now available to encrypt the SSN data that resides in the VSAM Remarks field. The custom inbound and outbound adapters that the user is passing through the xml file gets applied over the SSN. As a result, SSN now appears in a disguised format in the output file.

Topaz for Total Test

Fix is available to allow shorter length copybook to be added for fixed-length record files.

Test scenario fails to execute SQL statement from the web application. The fix is now available.

 The REST Service component is failing when the response contains CDATA tag or when user is trying to log response body. The fix for this issue is now available.