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.
• The Xpediter Batch Debug Profile has been enhanced to allow for simplified configuration for Code Coverage. It is now possible to browse for Code Coverage Repositories, Systems, and Test IDs and drop-down lists are now automatically populated with most recently used lists. Code Coverage repositories used in the Debug or Topaz for Total Test configurations are automatically added to the Code Coverage view.
• Execution Suites have been added to allow a list of File-AID/EX specifications to be executed together, in the order specified in the suite definition. Execution Suites may contain Related Extract, Related Loader, ConverterPro, and ComparePro specifications as well as other Execution Suites. They replace ConverterPro Sets, ComparePro Sets, and the Batch Execution Utility.
• Export functionality available for File-AID/EX specifications has been enhanced to export as batch so that the specification can be run as part of a batch jobstream in Windows or UNIX without requiring access to the repository.
• Code Coverage support has been added to the Test Run dialogue. You can automatically bring up a Code Coverage report after running your test case by editing your preferences. (Requires CSS 17.2 PTF CXS360A and Xpediter/Code Coverage 17.2 PTF PA01563.)
• The behavior of Topaz Workbench Help via F1 key now launches help in an Eclipse view vs. opening Help contents in a separate Window. The F1 key behavior is now consistent with standard Eclipse behavior.
• Allows search (both File-AID Dataset Search/Update and Host Explorer Dataset Search) at the Host Explorer z/OS Datasets filter level. The user will be prompted if this filter includes migrated datasets.
Additionally, to use the File-AID/EX and File-AID Data Privacy features that are available in Topaz Workbench, users must install the appropriate options listed above and install the following features during Topaz Workbench installation:
All Related Extract and Related Loader specifications will now open in Topaz Workbench editors. If the existing specification contains any features that are not supported in Topaz Workbench, a message listing the unsupported features appears and warns that these features will be dropped from the specification if it is opened in Topaz Workbench. The following features are not supported:
• Single Signon. You will now be able to use your existing common Compuware HCI connection with ISPW. See the Topaz Workbench 18.2.1 Installation Guide for detailed upgrade instructions, including configuration changes required to connect to ISPW from Topaz Workbench.
-- When used together, ISPW Eclipse and ISPW must be on the same release level to enable single signon. If your site intends to use ISPW in Topaz Workbench, Compuware recommends that you install the latest version of ISPW before installing the latest version of ISPW Eclipse.
Most Related Loader specifications created in standalone File-AID/EX can now be opened in the new Topaz Workbench Related Loader Editor. When importing a specification created in standalone File-AID/EX that has features that are not yet supported in Topaz Workbench, a warning message appears identifying the unsupported features. Saving the specification for use in Topaz Workbench will drop the unsupported features.
• When a specification is saved, it is saved in the new format within the existing File-AID/EX repository structure. Warning messages requiring user confirmation prevent accidentally overwriting a specification created by standalone File-AID/EX with a new Topaz Workbench specification.
The Application Audit plug-in for Topaz will no longer be shipped with Topaz Workbench, in favor of the new browser-based user interface available with Application Audit, which has been available since April 2017. Support for the Application Audit plug-in for Topaz will continue until July 1, 2018.
The Xpediter/Eclipse TSO debug session type is being deprecated in release 18.2.1, but will continue to be supported until July 1, 2018. Xpediter/Eclipse’s Batch debug session type will replace the functionality and should be used instead.
The Preprocessor Compile and Postprocessor Compile options under the Configure > Compile menu in Topaz Workbench have been removed in the 18.2.1 release. To automatically create Compuware source listing members (DDIO), you can add Compuware Shared Services language processor JCL to your SCM generate process or compile JCL. You can also perform an on-demand conversion of your source listing to DDIO when viewing an abend in Abend-AID.
Collaboration Perspective has been removed in the 18.2.1 release. Customers wishing to share information created by Find and Fix Requests can do so by leveraging JIRA integration in Abend-AID and iStrobe, or by exporting the Find and Fix requests and sharing via email.
• When the specification is saved, it is saved in the new format within the existing File-AID/EX repository structure. Warning messages requiring user confirmation prevent accidentally overwriting a specification created by standalone File-AID/EX with a new Topaz Workbench specification.
• Ability to browse ESS listings that are embedded within a load module. This allows you to navigate through a DDIO file in the same way you would if it were in standard DDIO, shared directory, or database format.
• Data records written (using the ESS command) to the executable binary are identical to the DDIO records written to the DDIO files. Therefore, executable binary size increase will approximate the size of the DDIO file member in the listing DDIO files.
• 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 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.
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.
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.
• If Topaz Workbench plugins are installed in Eclipse 4.4.2 or 4.5 or RDz 9.5.1, updating the plugins from 17.2.n to 18.2.0 will break the copybook download functionality for source members defined in online projects.
• When a source code member in a project is brought into an edit session, there is no prompt to download copybooks. Consequently, there is no support within the source via F3 or Go to Definition on the Copy statements. This occurs in existing projects and new ones created after the update.
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.
An error may occur if a pre-5.0 Topaz or Workbench Assembler, C, COBOL, JCL, or PL/I Compuware or Xpediter editor remains open in a workspace while a migration to a current release of Topaz Workbench is occurring. When Topaz Workbench is opened an error will indicate that the editor type is not supported. To resolve this issue, close the editor and reopen the file.
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.