Release notes: Version 20.10.01 of BMC Compuware Topaz Workbench

Additional information for variables

When you point the mouse over a variable within the PL/1 and COBOL editors, you can now see additional details such as ISPW repository location and line number information of that variable.

Enhanced actions for Sandbox Codelines

You can now Promote or Regress tasks in a Sandbox Codeline.

Regress and Promote action completion status in Console view

When the Regress or Promote action is initiated and completed, the Console view is updated with success and failure messages to indicate the status of the completion of the action.

Multi-color level in the ISPW life cycle

The ISPW life cycle has been updated to show a multi-color level when it contains Sandbox and non-Sandbox tasks at the same level.

For a selected task that has other versions at the same level, the upper half of the rectangle is displayed in orange for the active version in life cycle, while the lower half of the rectangle is displayed in gray for other versions in the life cycle.

Dynamic resizing of Add Task dialog box

The ISPW Add Task and Add Task with Checkout dialog boxes now resize dynamically. This lets Eclipse decide the default size for the dialog box.

Additional version details in Replace Version dialog box

You can now view more information about versions in the Replace Version dialog box when you choose to replace the current version with another version in the life cycle . For more information, see Update-Replace-Component-Version.

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.

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

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.

ISPW/Eclipse

After logging on to Topaz Workbench with the Japanese host code - 930, when you perform Add to Assignment with Check out, Topaz Workbench does not respond.

Topaz Enterprise Data

Fixed the issue CTL-F - Find and Replace under Edit option not working. Deleted two deprecated key schemes that were showing up in customer environment. 

Topaz for Total Test

Adding timestamp in the all type of reports and copy the same reports into the History folder. All output files are saved in the history folder, if the "Save time stamped files" is checked in project properties under the "Topaz for Total Test".

As per the COBOL numeric range signed/unsigned values are entered and stored in the stub numeric values.

Restored the link to TTRUNNER output in a Virtualized Test report.

Duplication of "Folder Name" Text field from "New Topaz for Total Test Project" window is removed.

Enhanced validation of repository server URL to prevent invalid/malformed content from being saved in user preferences.

Always read the HCI Configuration and XaTester Host config files with encoding as UTF-8.

Fixed issues related to:

• Local JCL selection.
• Wrong repository selection status in the log.
• Refresh of history in Test Suite and Test Scenario.
• Listing history in Test Scenario.
• Navigation to Test Scenario from Detailed Report of Test Suite.

Fixed the JCL error reported as "UNIDENTIFIABLE CHARACTER or "UNIDENTIFIED OPERATION FIELD" after copy/pasting JCL into the File-Aid Compare component for a functional test scenario.

Fixed an issue where field starting with RETURN-CODE interfered with resolving actual program RETURN-CODE.

Removed the TTT console and write messages to the Compuware console.

Handled access type for caching credentials for frequent communication to the mainframe.

Using the Job Submit element with no jobcard defined.

Right click menu unavailable from repository view.

Fixed the issue where Bytes are incorrectly populated while editing a record structure.

Corrected the position of cursor when creating a new Total Test suite.

When no TTTTRUNNR loadlib is defined for a connection, open the To talTestConfiguration project and select the connection that needs to be updated.

Encryption protocol added as CLI argument via Jenkins.

All references to the Log4j have been removed from TTT features.  All logging is being done by a central Topaz logger.

Fixed issue where deleting value of numeric field set value to spaces instead of nulls.

Fixed the CICS argument length calculation with redefines and occurs.

Added Total Test CLI support for RACF PassTicket.

Bytes value is not editable for structures.

Environments in the Repository View can be scrolled.

Populate collector IP and port for IBM Code Coverage.

Fixed the issue with CICS report mentioning record not executed.

Address is updated for Git authentication.

Fixed the Redefine action which was not working for ArrayType structure.

Supports encryption protocol using local TotalTestConfiguration project

Fixed the wait for jobs HELD status by ThruPut Manager.

For "Write Records" palette item, from Setting tab - 'Get Setting' button for dataset is not working - getting error "Unable to get setting for dataset."

Resolved the issue for picking structure for copybook if the mainframe project type is online.

Topaz Workbench

Added a fix for a consistent Tab behavior even at the end of the document.

Fixed the InsertNewLineInTextRule for hebrew text in sequential and identity area.

Handling Null Pointer Exception and setting the default dimensions if they are empty.

PL/I Editor: programs where the module name is constructed inside a copy book will now have a correct top node in the outline view.

Added Grammar to support  RESULT_SET_LOCATOR/RESULT-SET-LOCATOR SQL type in Cobol parser

Resolved error due to NPE occurring during visualizer import operation

Fixed context sensitive help for the Topaz Editors.

A local file left open in an editor when closing Topaz will reopen in the editor without a "Resource not found" error when restarting Topaz.

Added code to check the line completion if it has multiple pairs of parenthesis.

When editing a running STC JCL from JES Explorer, Refresh duplicates all the JCL lines if the cursor is on a DD statement. A restriction was added to avoid duplicating the log details in response from HCI and update the new logs only.

PLI Parser Error - extraneous input ')'. The parser grammar was not handling zero arguments in optionsSpec.

PL/I parser error: invalid statement 'Call GenerateLine' when source contains a procedure call from another procedure.

PL/I parser does not complete : The code was not handling goto Statements to the full extend if present within the loop

PL/I parser error: missing semicolon at 'IN'. The parser grammar was not handling IN option in a free statement.

PL/I parser error: extraneous input '3'. The parser grammar was not handling level for factoring attributes enclosed in parenthesis under Declare Statements.

PL/I parser error: mismatched input '=>'. The parser grammar was not handling locator Qualifier and variable Reference within a function Invocation call.

PL/I parser error: mismatched input '('. The parser grammar was not handling variable Reference in a Signal condition statement.

The PL/I parser error:

PL/I parsing grammar was modified to support EXTERNAL Keyword along with string literal in left and right parenthesis.

Ensure that the PL1 preprocessor correctly concatenates single-quoted strings.

Example: external('ckcifa')

The PL/I parser error.

In the case of Nested Procedure calls, the declaration for the parameters in the procedure was causing the value to be passed as empty. Additional validation has been added to verify if the values received for the parameter in the initial call are the same as the ones in the nested procedures.

The PL/I parser error: extraneous input '.' expecting THEN FLOAT.pli

Grammar for decimal literal has been modified to make the Integer value present after the decimal value as optional.

The PL/I parser error: extraneous input 'ENTRY' expecting SEMICOLON

PL/I parser grammar error for a declare Implicit Entry statement that had the ENTRY option specified.

The PL/I parser error: invalid statement 'when('

Handle PL/I preprocessor replace statement that was stripping quotes.

PLI parser gets support to correctly parse the § character when user logs in with code page 1141

As per the mainframe logic, the "*Process" keyword should start from the 1st column of the document. So we added this additional check in the preprocessor code when the "Process" keyword is found.

Fixed the Tab & Shift Tab Inconsistencies so that it now works same as Eclipse along with a support to variable tabs.

PL/I preprocessor: Provide better line wrapping support for AnswerStatement to allow for SKIP options, the column option, and custom margins.

Fixed Ambiguous variable issue from the second occurrences of same variable from different procedure in the same file

Copy (Ctrl+C) from one file and Paste (Ctrl+V) into another file not working correctly. All the copied records on one line with end of line changed by null.

Added extra rule in parser grammar along with the semicolon instead of optional semicolon so that it could support the proc call.

When we paste the multiline text in the end of file or new file, we have set the default delimiter (new line character) instead of null delimiter so that the text should be pasted in the existing format.

Added extra rule in parser grammar along with the semicolon instead of optional semicolon so that it could support the proc call and RCPTT

Cobol editor: If there is an error in a copybook, and Sequencenumber area and/or Identity area are locked, problem markers will be in the correct position in the copybook source file.

Fixed corruption of the when condition breakpoint during an Xpediter test.

Handle array dimensions that use variables.

Fixed error message when copying to GDG fails due to out of space.

Fixed context sensitive for Xpediter\Eclipse.

Updated the Javadoc for API examples to java 1.8 as it was not showing java doc  for methods with more than 1 parameter.

Handle NPE and checked Pl1 colorization is correct when two pl1 files are compared with each other and default editor is selected as pl1 editor to compare. Fixed dropdown label issue to display correct label as per selection.

When Topaz starts up, JCL files that were left open in General projects were not opening properly.

Cobol sort buttons for Outline view do not seem to work properly.

Sorting will now sort alphabetically even when using mix case.

Cobol Shift tab has inconsistencies.

The COBOL Editor tab and Shift tab keys now work the same as eclipse text editors, with the addition of variable tab support.

Topaz Cobol Editor - code folding does not stay folded after parser runs.

After editing and incremental parsing, ensure that code folding preferences are adhered to for redisplaying the source.

Host name changes after logging out.

Fixed host description changes after logging out of the host.

Topaz did not support opening embedded source member with names starting with *, throwing an exception because invalid file name.

Fixed by escaping the * with UTF-8 code. File will now properly open in editor.

The Cobol Editor's 'Editing' label is missing for open editor when Topaz Workbench (re)start.

Fixed missing content description for files that are re-opened when Topaz starts up.

Added support for copying text files within USS.

Upgrade Log4j from 1.2 to 2.17.1 to address security vulnerability CVE-2021-4104

When a user defines an undeclared variable, error markers are cleared. When a user deletes a variable declaration, code still referencing that variable is marked as an error.

All RRDS file types can be actionable in Host Explorer.