Topaz Workbench provides an Eclipse-based IDE to streamline mainframe application development with System z software. Its intuitive and easy-to-use interface provides the essentials of modern mainframe application development, testing, and maintenance powered by Compuware Abend-AID, File-AID, Hiperstation, Xpediter, and Strobe.
The Topaz Workbench media is composed of Topaz Workbench, a branded Eclipse Rich Client Platform application that includes the Compuware z/OS Product Plug-ins. Topaz Workbench plug-ins are also made available on the Topaz Workbench media for installation into Eclipse and IBM RDz/IDz environments.
-- An embedded emulator accommodates one-off 3270 interactions without leaving Topaz. For example, you can run REXX/CLIST utilities within ISPF or access CICS or IMS transactions to initiate debugging sessions.
-- The Topaz Enterprise Data feature selected during install now includes functionality which was previously installed by the File-AID/Eclipse, File-AID/EX, File-AID Data Privacy, and Topaz for Enterprise Data features.
-- All functionality from File-AID/EX is now available from within Topaz Workbench. Installation of the Topaz Enterprise Data feature within Topaz Workbench includes the File-AID/EX client, Communications Manager, and a local Execution Server. The File-AID/EX standalone client components which were previously installed from the File-AID/EX tab on the Topaz for Enterprise Data media are now part of Topaz Workbench.
-- Since File-AID/EX functionality is now installed with Topaz Enterprise Data, it can only be started from within Topaz Workbench; there is no longer an option to start File-AID/EX from the Windows Start Menu.
-- Related Extract now includes an option to generate Delete statements for each row included in the extract. A file is generated containing the Delete statements; this file can then be processed as SQL to delete the identified rows.
-- Execution Servers are now defined as preferences for Topaz for Enterprise Data. An option is available to add current Execution Server definitions stored in the repository to TED Preferences. Execution Server Preferences includes Execution Hosts to identify hosts for mainframe execution.
-- This is the first initial integration between unit and functional testing and shows how the integration of the approaches will be done. Improvements will be made for each coming release based on customer interactions and feedback.
• A new Promotion Analysis column has been added the to Active Assignment view which will warn of potential overlay conflicts; this is the information found in the “Version Audit” report in the TSO interface
• Improved the ability to control the logical layout of mainframe projects, allowing cut/copy/paste of mainframe assets (files, tables, members, launch configurations) across folders and across mainframe projects.
• Introduced the Common tab to the Launch Configuration dialog. This tab replaces the Comments tab and allows the user to save the configuration within a project (besides the ability to add comments).
• Extracts can now be created in Topaz for Enterprise Data for File-AID/RDX. Extract is available for z/OS Db2 tables and includes the ability to discover related tables based on RI defined in Db2, specify selection criteria, define extract options and apply Data Privacy rules. The extract can be saved to a repository and executed by File-AID/RDX; execution reports will be returned to Topaz for Enterprise Data.
• Metadata Extensions are used by Data Privacy Rules to process COBOL layouts which contain REDEFINES. The Metadata Extension defines which definition or REDEFINES is to be used to process the data. Metadata Extensions have been redesigned to allow reuse of the definition and improve usability. Previously, the use of a Metadata Extension was limited to the dataset and member specified during definition. Metadata Identifiers have been introduced to provide additional locations where the same layout resides. The same Metadata Extension definition will then be applied to each layout identified by the Metadata Identifiers.
• The ability to disable Source Data Identifiers (SDIs) in the Data Privacy Global Project is no longer available. Any existing SDIs within the Global Project will be enabled during repository conversion. SDIs imported from the Global Project must be disabled within the Project which uses the SDIs if they are to be omitted during processing.
• Data Privacy now includes Encryption Sets which allow users to limit the characters used as replacements during encryption rule actions. A new function was added to Administration to define the Encryption Set.
-- The view now has three panels, including a collapsible dialog on the left for entering search criteria. The middle panel will show the jobs in the queue, and the right side will show the DDs for the selected job. A filtering capability has been added for the jobs that appear in the middle panel as well as the total number of records for the selected jobs DDs.
-- Additionally, DIFFZilla has been added as a compare option for comparing source code. DIFFZilla allows columns to be ignored in the comparison, which can be useful when source code line numbers are part of columns 0-7 or 72-80.
• Security improvements were made to File-AID/EX to provide secure socket communication and password encryption. A utility was added to generate key stores and trust stores for securing communication.
• The File-AID/EX installation instructions and the File-AID Data Privacy Configuration Guide are now part of the Topaz Enterprise Data Installation and Configuration Guide . A section on “Good Practices” for security has been added to this guide.
• Topaz CLI for ISPW now supports downloading of specific Set, Assignment, or Release containers as well as downloading of changes (instead of complete download) on subsequent runs of the downloading process.
The following features need to be installed after Check for Updates upgrade processing of an earlier 19.x release to Topaz 19.4.1 has been performed. Refer to the Topaz Workbench Installation Guide , Appendix C, “Adding and Removing Topaz Workbench Features”.
• Generating Topaz for Total Test unit test cases for very large programs may require increasing the memory allocated to Topaz Workbench. To do this edit the topaz.ini file in your installation directory of Topaz Workbench (by default the path is C:\Program Files\Compuware\Topaz Workbench\eclipse):
• If Topaz Workbench Datatools will be used, install only the Compuware DB2 for z/OS using Topaz (base) feature. This plugin is optional and not required if the native Eclipse datatools plugins will be utilized.
• To use Topaz Workbench Datatools after the Compuware DB2 for z/OS using Topaz (base) feature has been installed, a database connection must be established. In IBM IDz 14.1 releases, the New Connection Profile option in the Data Source Explorer view does not open the correct dialog. You must:
If you wish to run a new installation of Topaz Workbench as 32-bit in a 64-bit environment, run the Install32on64.bat file, which launches an installer containing an option to install as 32-bit on 64-bit. The batch file is located in the same folder on the Media Browser disk image as the setup.exe file.
Starting with release 19.4.1, a 32-bit Java Virtual Machine is no longer packaged with File-AID/EX. The default location for the 64-bit JVM is the C:\Users\<User ID>\Compuware\Topaz\eclipse\jre folder. Windows registry is no longer used, and existing registry entries are automatically moved to configuration files. If you have customized batch files or JVM switches, review them to ensure they remain compatible after the change to a 64-bit JVM.
Use of Host Explorer and SlickEdit will require 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.
• Security for the Hiperstation for WebSphere MQ product is now checked not only when the product is started, but also whenever a Restart command for a global recording request is issued. If security has changed for the request owner or rules have been changed, requests that ran before may no longer run.
eGit versions 4.6.1--5.0.1 and 5.04 and above are compatible with Topaz Workbench release 19.01 and above. eGit versions 5.02--5.03, however, exhibit known issues with the eGit UI and are not compatible with Topaz Workbench release 19.01 and above.
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 (default 512m or 1024m) used to specify the maximum heap size. The optimum value for this parameter varies depending on the OS used, memory fragmentation, and other factors.
On 32-bit Windows, the theoretical heap size is limited to 2GB due to how Windows allocates memory, but this is reduced by many factors. Generally, the stated maximum is 1536m, while a commonly stated max range is 1200m to 1500m. 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. Compuware recommends 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. The only practical solution in such situations is to install the products on a 64-bit OS.
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 4GB or more for the Xmx parameter can be practical depending on the Windows virtual memory size.
When exporting an image from Program Analysis or Visualizer, if the View document after export checkbox is selected, *.png is selected from the Save as type dropdown list, and the default application associated with .png files is Microsoft Paint, the exported image cannot be opened automatically. Browse to the export location and open the file manually.
When using Program Analysis, markers for Information items can potentially overlay and obscure Error and Warning markers in the SlickEdit Overview Ruler. The suggested workaround is to deselect the Overview Ruler for Information items, leaving Errors and Warnings displayed without being overlaid.
The topaz.ini file sets the osgi.instance.area.default to the @user.home location, which is typically mapped to a local drive or absolute path. If the user has their @user.home set to a UNC network path, the toolbars and menus within Topaz Workbench may not appear. To correct the problem, edit the topaz.ini file (default location is Topaz Workbench installation’s eclipse directory), replacing the @user.home location with a local drive or absolute path. If Topaz Workbench has been installed via p2repo into an Eclipse instance, the edit should be done to the eclipse.ini file instead.
Microsoft Internet Explorer cumulative security update KB2977629 can cause failure of Eclipse-based products when closing the Welcome page. To resolve this issue, install Microsoft Internet Explorer cumulative security update KB2987107 or uninstall KB2977629.
The potential exists for loss of precision on FLOAT and DOUBLE data types between the mainframe and the File-AID Data Editor user interface. See “Chapter 9. Floating-Point Overview and Support Instructions” in IBM's z/Architecture Principles of Operation (SA22-7832-09) for more information.
Picture clauses for COMP and COMP-4 (binary data) field types are not used when displaying the decimal numeric value of these fields. Any implied decimals (V) or implied scaling (P) in the Picture are ignored and not used to display the numeric value of the field. The value displayed is a positive or negative integer.
The ruler at the top of unformatted mode is intended to line up with the data below it, but this may not always happen. Although the same fixed-width font is used for both the ruler and the data, certain characters on code pages 930 and 939 are narrower than others, causing the ruler and the data to fail to line up when those characters appear in the data.
The recommended solution is to substitute the narrow characters with red “periods” as currently done for binary data that cannot be translated to characters. Any modifications to those letters and punctuation must be done in the 3-line Hex display option.