Release Notes

Topaz Workbench 18.02.06

March 2, 2018

What’s New in Release 18.02

Software and Hardware Requirements

Technical Notes

Known Issues

What’s New in Release 18.02

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 Topaz Workbench Release Notes include all information--such as new features, system requirements, technical notes, and known issues--for Topaz Workbench.

Release 18.02 includes the following enhancements:

Note: Current releases contain the latest maintenance for Topaz Workbench which addresses stability and reliability issues identified since the previously available release.

January 4, 2018

Topaz Workbench has been enhanced as follows:

Xpediter/Code Coverage

  Code Coverage repositories can now be created from Topaz Workbench in the Code Coverage View or via the File > New > Other > Compuware wizard. (Requires CSS 17.2 PTF CXS360A.)

  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.

  There is now an option to automatically display a Code Coverage report after a debug run.

  There is now an ability to clear out existing Code Coverage statistics before a debug session to allow users to view code coverage metrics only related to the most recent execution.

  The Report and Filter nodes in the Code Coverage view have been renamed to Report Requests and Report Filters to better reflect the functionality.

  Code Coverage reporting configuration has been simplified to improve usability. The Host and Code Coverage repository have been moved from the Preferences to the Report Request dialog.

  The Report Request dialog has been switched from a wizard to a tabbed dialog to streamline usability.

Enterprise Data

  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.

  Execution for File-AID/EX specifications has been enhanced to include selection of the Execution Server where the specification is to run.

  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.

  A new view is available to list all File-AID/EX specifications. Execution Logs are now displayed in this view and have been removed from the File-AID Explorer tree view.

  Support has been added for schema filters in Related Extract.

  New options have been added to Related Loader to choose whether the clear rows option will use database delete or truncate processing and to create constraints before loading.

  Modified date is now available for each File-AID/EX specification.

  Execution history can now be cleared from the Console.

  Cross-LPAR Compare can compare MVS files that exist on different LPARs. (Requires File-AID Common 17.2 PTF PA01559 and File-AID/MVS 17.2 PTF PA01560.)

Topaz for Total Test

  Topaz for Total Test supports DB2 assertions on OPEN, CLOSE, INSERT, UPDATE, DELETE, and FETCH.

  Topaz for Total Test now has support for DB2 ROWSET.

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


  Jenkins plugin that executes ISPW Actions using our APIs, making it much easier to bring ISPW into your toolchain.

  You can now do a Promote against a Container in the Container View.

  Performance improvements including more efficient logging.

  Added ability to easily browse a Set Log from Container and Task Views.

Topaz Workbench

  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.

  The default behavior of SlickEdit Find dialog is now to remain open to allow repeated Find commands to be more easily issued.

  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.

October 2, 2017

Topaz Workbench has been enhanced as follows:

Topaz for Program Analysis

  Topaz for Program Analysis has improved handling of large runtime and program visualizations, including the ability to limit the text associated with nodes and to hide or isolate the view to nodes.

  Runtime visualizations now provide call stack information for a given node.

  Program Analysis now provides the ability to show the calling and called routines within the structure chart.

  Added the capability to export Program Analysis data displayed in tables.

Topaz for Enterprise Data

  The File-AID/EX and File-AID Data Privacy features of Topaz Workbench are now included as part the Topaz Enterprise Data feature.

  The Related Loader feature now allows Expressions within Column Mapping.

  Application Relationships now has a new editor for maintaining relationships.

  File-AID/EX ConverterPro has a new utility to replicate specifications and adjust connection information.

Topaz for Enterprise Data Media

New media, called Topaz for Enterprise Data, has been created for installing the following:

  File-AID Services

  File-AID Rules Engine


  File-AID Execution Servers.

This new packaging means that, starting with release 18.02.03, File-AID Data Privacy and standalone File-AID/EX are no longer ordered as individual products.

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:

  File-AID/EX feature

  File-AID Data Privacy feature

  Topaz for Enterprise Data feature (allows use of Enterprise Data Editor and Data Visualizer).

File-AID/EX in Topaz Workbench

The File-AID/EX feature in Topaz Workbench includes the following components:

  Related Extract

  Related Loader

  Selection Criteria

  Application Relationship Editor.

These components no longer exist in standalone File-AID/EX.

The following components exist in standalone File-AID/EX but can also be launched from Topaz Workbench:



  Batch Execution Utility.

Migration of Specifications

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:

  Embedded Privacy rules

  File encryption and decryption

  Related Extract options:

-- Dependents to fetch count

-- Schema filters

  Related Loader options:

-- Create contraints before load

-- Lookups during related loader

-- DB2 remote load

Topaz for Total Test

  Topaz for Total Test now has support for DB2 stored procedures. The stored procedures support is limited to External COBOL stored procedures.

  Write assertions can now be created for Test projects for DB2.

  DB2 ROLLBACK and SAVEPOINT commands are now supported.


  A target folder can now be specified when using Copy to Workstation.

  The Components View now includes an embedded filter.

Topaz Workbench

  Host Explorer now provides the ability to copy a dataset name to the clipboard.

  Smartcard and PassTicket authentication capabilities are now provided in Topaz Workbench. Previously, these capabilities were packaged separately and made available upon request.

  Deploying Topaz Workbench to end users via a silent install script now allows the target Topaz Workbench install directory to be customized.

  Host Explorer provides more detailed information in the confirmation prompts when deleting datasets, members, or filters.

  When creating dataset filters in Host Explorer, examples are now provided to help users understand dataset filter syntax, including wildcard specifications.

June 28, 2017

Topaz Workbench has been enhanced as follows:

Topaz for Total Test

In this release, Topaz for Total Test adds:

  The ability to create Data Stubs for DB2 calls: OPEN-FETCH-CLOSE, SELECT, UPDATE, INSERT, and DELETE.

  New options for import and export of Excel spreadsheet.

  The ability to set Job Card preferences.

  The ability to set a high level qualifier in Topaz for Total Test preferences.

  Topaz for Total Test Jenkins plugin to run unit tests from Jenkins.

Note: Topaz for Total Test 18.02.01 requires:

-- Xpediter/TSO Release 17.02 with current cumulative maintenance

-- Enterprise Common Components (ECC) Release 17.02 with current cumulative maintenance

-- Topaz Workbench 18.02.01.

ISPW Plugin for Eclipse Enhancements

The ISPW plugin for Eclipse has added the following improvements:

  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.

-- Requires an update to ISPW on the mainframe, HCI, and CSS 17.2 PTF CXS105A.

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

  A new Import Local File option to import only new items in a folder, and more choices when current versions exist.

  A new Jenkins Plugin for source retrieval. This will allow you to get Topaz for Total Test assets from ISPW to run automated tests.

  The Repository Explorer has been improved to add the following right click options:

-- Add to Assignment

-- Add to Assignment with Checkout

-- A new Import Local File option to only import new items in a folder, and more choices when current versions exist.

  Continued enhancements to the Components View, including the addition of an Open Action.

CES (Compuware Enterprise Services) Security Authentication Enhancements

  Topaz Workbench now supports CES instances configured for authentication.

  Supported Authentication Modes are Internal, LDAP, Kerberos, and Client Certificate.

  For Client Certificate Authentication, the proper certificates must be loaded in the keystore of the JVM used to execute Topaz Workbench.

  The Compuware Enterprise Services Preference Page displays and validates the CES Authentication Mode.

File-AID/EX in Topaz Workbench

Additional File-AID/EX functionality for Related Loader is now available within Topaz Workbench; File-AID/EX 16.03.09 is required for this functionality.

Topaz Workbench Related Loader Editor

Topaz Workbench Related Loader Editor is included in the File-AID/EX perspective. The editor now allows users to do the following:

  Change the target table name.

  Specify execution time credentials.

  View source table metadata.

  Map source columns to target columns.

  View and edit DDL used to create tables.

  Specify Load Utility options for DB2 and Oracle.

Export and Import Related Loader Specifications

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.

The following Related Loader features are unsupported:

  File encryption and decryption

  Embedded Privacy Rules



Coexistence of Standalone File-AID/EX and Topaz Workbench

The following information applies to the coexistence of standalone File-AID/EX and Topaz Workbench:

Related Extract and Related Loader specifications created or edited in Topaz Workbench cannot be edited in standalone File-AID/EX.

Within the File-AID Explorer view, the icon displayed for each specification differentiates specifications created in Topaz Workbench from those created in standalone File-AID/EX.

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.

Application Audit Plug-in for Topaz

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.

Xpediter/Eclipse TSO Debug Session Type

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.

Preprocessor Compile and Postprocessor Compile

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

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.

If you are in any way impacted by the removal of these features, please contact Compuware Customer Support. (See below.) They can arrange a call with Compuware Product Management to discuss further.

April 3, 2017

Topaz Workbench has been enhanced as follows:

Topaz for Total Test

In this release, Topaz for Total Test adds:

  The ability to create Data Stubs for VSAM KSDS, ESDS, RRDS

  New options for creating Data Stubs in Generate Unit Tests

  Support for installation into IBM Rational Developer for z Systems (RDz).

Note: Topaz for Total Test 18.02 requires:

  Xpediter/TSO Release 17.2 with current cumulative maintenance

  ECC 17.2 with current cumulative maintenance

  Topaz Workbench 18.02.

Visualizer Improvements

This release incorporates the following enhancements specifically designed to assist in analyzing large visualizations:

  Connectors from data objects now represent the direction of data flow: arrows pointing from a data object indicate INPUT requests, and arrows pointing to a data object represent OUTPUT requests.

  Visualizers now let you reclaim display space by redrawing a complex visualization after you’ve collapsed nodes.

  Runtime Visualizer now includes a right-click Show In choice that allows you to:

-- Filter either the Summarized Events or Individual Events by a node name or a connector to see the events specific to that object.

-- Open a Call Stack view for an object showing the call stacks--or optionally the reverse call stacks--to that object.

-- Open a Call Stack Text view showing the complete call stack for the execution. The view can also be exported for later analysis.

  Runtime Visualizer has added a ROOT node above the first program node. This is to better handle the case where your execution is multi-threaded.

ISPW Plugin for Eclipse Enhancements

The ISPW plugin for Eclipse has added the following improvements:

  The Components View added:

-- Quick Search

-- Add to Assignment.

  Repository Explorer added:

-- The ability to search for a component by name or type

-- More flexibility in what is displayed: Selected Level Only; First found in level and above; and All found in level and above.

-- A new Import Local File option to only import new items in a folder, and more choices when current versions exist.

  Custom Generate Dialogs support to assist you in aligning with what you have in ISPF.

File-AID/EX in Topaz Workbench

Selected File-AID/EX functionality for Related Loader is now available within Topaz Workbench; File-AID/EX 16.03.08 is required for this functionality.

Topaz Workbench Related Loader editor is now included in the File-AID/EX perspective. This editor allows users to do the following:

  Create a new Related Loader specification based on an extract specification stored in the File-AID/EX repository, the File-AID/EX extracted data file or an extract file produced by File-AID/RDX

  Select the host and database where the data is to be loaded

  View list of tables and choose which will be loaded

  Change the schema for selected tables or for all tables

  Specify SQL Insert options

  Automatically create tables in the target environment

  Execute the specification to load data into the target environment.

Note: The following information applies to the coexistence of standalone File-AID/EX and Topaz Workbench:

  Related Extract and Related Loader specifications created or edited in Topaz Workbench cannot be edited in standalone File-AID/EX.

  Within the File-AID Explorer tree, the icon displayed for each specification differentiates the Related Extract and Related Loader specifications from those created in standalone File-AID/EX.

  Editing Related Loader specifications created in standalone File-AID/EX will launch the File-AID/EX Wizard; they cannot be opened by the Topaz Workbench Related Loader.

  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.

Embedded Source Support in Topaz Workbench

The April 2017 Topaz Workbench 18.02 release provides the following new functionality for Topaz Workbench:

  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.

  Users can now browse the embedded DDIO member within PDSE load libraries. A load module may contain one embedded DDIO per CSECT, so multi-CSECT load modules may have many embedded DDIO members.

  Xpediter/Eclipse can debug modules with ESS data. There is no impact on the end user.

  If Xpediter detects ESS data, it will be used, and no further searching will be done for DDIO files in standard DDIO, shared directory, or database format.

Note: ESS usage considerations:

  ESS is only available for COBOL programs and the IBM Enterprise COBOL compilers starting with V5.1

  IBM Enterprise COBOL V5.1 and higher require the use of a PDSE for executable binary libraries.

  All previous DDIO functionality remains unchanged and in place.

  ESS is an additional command that can be used instead of DDIO.

  ESS and DDIO commands are independent and can be used separately or combined.

  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.

  Compuware source solutions have been changed to first look for the ESS records and, if found, will not search for any DDIO file.

  If the ESS records are not found, the usual DDIO file search mechanism, as currently implemented in each of Compuware’s solutions, will be used.

  The following PTFs are required to enable ESS:

-- Compuware Shared Services 17.2: CXS128A

-- Xpediter/TSO and IMS 17.2: PA01003

-- Xpediter/CICS 17.2: PA01010-PA01014

-- Xpediter/Code Coverage 17.2: PA01098

Software and Hardware Requirements

The Software and Hardware Requirements can be found in the Topaz Workbench Installation and Configuration Guide.

Technical Notes

Topaz for Total Test

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

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

  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):

Find the entries:


Change them to:


This change doubles the amount of memory available to the Topaz Workbench and Topaz for Total Test.

Save the topaz.ini file and restart Topaz Workbench.


Supported DB2 and IMS Releases


-- V11 CM, NFM

-- V12 (Refer to File-AID for DB2 for further support details)


-- IMSV12.1

-- IMSV13.1

-- IMSV14.1 (Refer to File-AID for IMS for further support details)

Supported Distributed RDBMS Platforms

  Oracle Database 11g, 12c

  DB2 for LUW V9.5, V9.7, V10.1, V10.5

  Sybase 15

  MS SQL Server 2005, 2008, 2012

Program Analysis

Supported COBOL, PL/I, DB2, and IMS Releases

  IBM Enterprise COBOL for z/OS:

-- V4.2

-- V5.1

-- V5.2

-- V6.1

-- V6.2

  Toleration of all supported GA versions of:

-- IBM Enterprise PL/I for z/OS

-- IBM DB2 for z/OS

-- IBM CICS Transaction Server for z/OS

-- IBM IMS Transaction and Database Servers.

ISPW Installation in Eclipse or RDz/IDz Environments

For the ISPW plug-in to be fully functional in an Eclipse or IBM RDz/IDz environment, be sure to select Host Explorer and SlickEdit (optional, for copybook support) for installation along with ISPW.

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

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.

VIPA Networks

A minimum of HCI 3.0 is required for VIPA networks.

Host Explorer and SlickEdit Licensing

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.


Compuware Shared Services Enhanced Listings

Xpediter/Eclipse does not support Compuware Shared Services (CSS) enhanced listings. For information on enhanced listings, refer to the Compuware Shared Services documentation.

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

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.


  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.

  Only single-byte characters are supported on code page 939.

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

Known Issues

Copybook Download Issue in Projects After Upgrade

Upgrade of plug-ins in non-Compuware branded Eclipse containers can cause copybook download to break in Project Explorer.

  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.

  This only affects online projects; copybook download functions properly in Host Explorer and ISPW Eclipse.

  This does not affect updates and new installations of Topaz Workbench.

Viewing Exported Portable Network Graphics (PNG) Files

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.

Overlaid Error and Warning Marks in Overview Ruler

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.

Potential for Missing Menus and Toolbars

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.

Compuware Editor and Xpediter Editor

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.

Internet Explorer 11 Security Update for Windows 7 and 8.1 Causes Topaz Workbench Failure After Closing the Welcome Page

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.

File-AID Data Editor

Potential Loss of Precision

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.

Formatting of COMP and COMP-4 COBOL Fields

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.

Unformatted Mode Ruler and Data Alignment

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.

Locked Oracle Table Postpones Timeout Error

When saving data to a locked Oracle table, the timeout error does not return after the set timeout period. It does return after the lock has been released.

Doc. JAN2018