Release Notes

File-AID Data Privacy 16.03

January 30, 2017

Obtaining the Latest Release Notes

What's New in Release 16.03

Software and Hardware Requirements

Technical Notes

Known Issues

Product Documentation

Support Resources

Obtaining the Latest Release Notes

For the most current version of these Release Notes , go to FrontLine , Compuware’s technical support website. The first time you access FrontLine, you are required to register and obtain a password. After logging onto FrontLine, select your product from the drop-down list. On the left side of the page, click the Documentation link. You will find the latest Release Notes listed with the other product documentation.

What's New in Release 16.03
August 2, 2016
Support for IBM Authentication Methods

To provide a higher level of authentication assurance for IBM z/OS applications, File-AID Data Privacy (with File-AID Common Components 16.03 PTF VJ16096) now supports the use of IBM Password Phrase Authentication for z/OS. File-AID Data Privacy does not support IBM Multi-Factor Authentication for z/OS.

January 4, 2016
Progressive and Classic Releases

Compuware is introducing a new release numbering system and will now offer two concurrent types of General Availability release: Classic and Progressive.

  Progressive releases provide the latest functionality and have a permanent release number, for example 17.02.00, where the first two digits are the upcoming year and the second two digits are the quarter of initial release. Licensees who choose Progressive releases acknowledge that their cumulative maintenance, which includes defect fixes and currency updates, may also require them to accept new functionality or reinstall with possible changes to the end-user experience.

  On January 1 of each year, the prior year’s Progressive release is transitioned to become that year’s Classic release. Cumulative maintenance on Classic releases will include currency updates and bug fixes, but will not introduce new functionality.

Although Progressive releases are generally backward-compatible with Classic releases of related products, new Progressive release functionality may require a related product to also be a Progressive release.

File-AID Data Privacy 16.03.02 is the Classic release as of January 1, 2016. From this point on, no new functionality will be added to File-AID Data Privacy 16.03. Maintenance will continue to be delivered during each quarter of 2016 and at planned increments beyond that.

Packaging and Name Changes

File-AID Data Privacy components will now be orderable as a separate product and will be packaged independently. The Compuware Workbench functionality has been integrated into the Topaz Workbench, so there will now be one Eclipse IDE offering. The default install of Topaz Workbench will include the File-AID Data Privacy client. The Compuware Workbench Server has been replaced by File-AID Services. The new File-AID Services media will include File-AID Services and the File-AID Rules Engine.

The Topaz Workbench and File-AID Services are required to create and maintain privacy rules and definitions for File-AID Data Privacy. Additional File-AID products are required to request the application of privacy rules depending upon what type of data is to be disguised.

  File-AID/Data Solutions is required for disguise of any mainframe data.

  File-AID/RDX is required for disguise of related data.

  File-AID/RDX or File-AID for DB2 can disguise z/OS DB2 data.

  File-AID for IMS is required for disguise of IMS data.

  File-AID/RDX and File-AID/Data Solutions can disguise z/OS files.

  File-AID/EX provides disguise for distributed data.

  File-AID Rules Engine must be installed on the appropriate platform.

Improved Composite and Overloaded Processing

Significant changes have been made to the definitions required for Composite and Overloaded processing. Processing types of composite and overloaded have been eliminated from the Data Element definition, and special rule types for composite and overloaded rules have also been eliminated.

Composite and Overloaded processing will now be handled as rule actions, and the definition needed for each will be included in the rule action. As part of migrating an existing Data Privacy Repository to the 16.03.02 release, all existing composite and overloaded rules will be converted to rule actions.

Handling composite and overloaded as rule actions allows the full functionality of rule logic to be available in conjunction with these rule actions.

Dynamic Data Items

New functionality has been added to rule logic to allow the values and expressions used to identify a data item during composite processing to be changed during execution. This provides highly customizable composite processing, as the rule logic can change how data is identified based on changes in input values.

List Variables in the Expression Builder

  Two new types of variables have been added: String List and Number List. These list variables can be used by the Expression Builder in rule logic or by user-written custom functions. Within the Expression Builder, there are several new functions to manage the values in the list, allowing values can be added, removed, and set as needed.

  Several UI changes have been made to include the new list variables, where appropriate.

Execution Parameters for List Variables

Execution Parameters can be provided to override the initial value of a variable at execution time. The syntax for execution parameters has been expanded to allow a list of values to be provided for list variables. This new syntax includes the ability to specify the delimiter being used between values.

Execution parameter support has also been added to File-AID/EX to extend this capability to distributed requests.

API for Data Privacy Rules

APIs are now available to request and apply File-AID Data Privacy rules. These new APIs can be used in two ways:

  A custom function can identify data and request that the disguise rules defined within the current project be applied.

  A standalone JAVA program can use the APIs to request that disguise rules be created for the metadata specified, and then to apply the disguise rules to the values passed in for disguise. The location of File-AID Services, together with the Repository and Project containing the disguise rules, is included in the API specification.

New Functions in Expression Builder
String Functions

New String functions have been added:

  COMPRESS – Compress consecutive whitespace

  PAD_LEFT – Pad a value on the left to the length specified using the value(s) provided

  PAD_RIGHT – Pad a value on the right to the length specified using the value(s) provided.

Data Privacy Functions

A new Data Privacy function has been added:

  IS_COMPOSITE_FAILED – Determine if the result of composite processing was successful.

Flow Control Functions

A new category of functions has been added for Flow Control with two new functions:

  SKIP_RECORD – Will stop disguise processing on the current record without making any changes and move to the next record.

  TERMINATE_PROCESSING – Terminate the entire execution.

File Functions

A new category of Resources has been added for Files. In this release, file support is limited to mainframe requests; the function will be ignored for distributed requests. At this point, only one file definition for DPRLOG is available. Any data written to DPRLOG in the rule logic will be written to whatever file is named on the DD statement for DPRLOG specified in the mainframe job.

Custom Functions

Custom functions will now be stored in the repository rather than as a file on the Workbench Server. This change will simplify the management of custom functions.

Two new custom functions are being provided to return Encryption and Hash results which are consistent with the results returned by embedded privacy rules; this consistency is limited to character fields.

These functions are included in the Samples directory for the client and must be added to the repository prior to use. The Resource Administration option for Manage Custom Functions provides this functionality.

   LegacyEncryptN will return the same results as the EncryptN encryption routine which is part of embedded rules in File-AID/Data Solutions and File-AID/EX.

   LegacyHash will return the same value as the Direct (D) or Hash (H) options of Translation in File-AID/Data Solutions and File-AID/EX.

Disguise of Additional Data Types

Disguise of CLOB and XML columns by File-AID mainframe products is available if File-AID 16.03 is installed.

Disguise of CLOB and XML columns by File-AID/EX is available if File-AID/EX 16.03 is installed.

Usability Improvements

Certain minor usability issues and defects have been resolved and may cause changes in the user interface.

Global Project

The content of the Global Project has been simplified and includes fewer samples. This will only be visible in new repositories.

Rule Selection and Conflict Messages

The rule selection process has been improved to apply rules in cases which would have failed. Also conflict messages have been reduced to eliminate duplicate messages and help identify the conflict.

See the Topaz Workbench File-AID Data Privacy User Guide for details on rule selection and conflict resolution.

Software and Hardware Requirements

The Software and Hardware Requirements (previously System Requirements) section of the release notes has been standardized across all Compuware Mainframe products and their Distributed components. Please note that any versions of third-party software that are no longer supported by their vendors under standard published contracts have been removed from the Software and Hardware Requirements section and placed in the Discontinued Support section of the release notes. However, any third-party software that was supported when this Compuware product went GA will continue to be supported until this product release has reached its End of Support date. No functionality has been removed from the product.

For further information about IBM System z software and hardware compatibility—specifically regarding IBM’s z/OS Recommended Service Upgrade, IBM’s Extended Address Volumes, IBM DB2 for z/OS, and z/OS product compatibility—refer to .

File-AID Data Privacy
Hardware Requirements

  Distributed Systems:

— Processor: 3 GHz minimum*

— Hard Disk: 1 GB minimum

— Memory: 2 GB minimum* (4 GB recommended)

* Processor speed and available memory directly impact performance. The faster the processor, and the more memory available, the better your performance will be.

Operating Systems

  IBM Mainframe

— IBM z/OS V1.12, 1.13, 2.1 (z/OS UNIX for File-AID Rules Engine)


— Red Hat Enterprise Linux for Servers 5, 6 (in 32-bit or 64-bit mode)

  Microsoft Windows 7 (x86, x64 mode), 8.1 Update (KB 2919355), 10

  Microsoft Windows Server 2012


  For supported Windows: Oracle Java SE 7 (build 60 or higher)

  For supported Mainframe: IBM Java 31-bit SDK V7.0 or higher (only 31-bit Java is supported on z/OS Unix)


  Compuware Products and Components

— Compuware Shared Services 9.0 (CXQ0315, CXQ0320, CXQ0354), 16.5

— Host Communication Interface 3.0, 16.5 (3.0 minimum required for VIPA networks)

— File-AID Common Components 10.1, 10.2, 16.3

— File-AID for DB2 10.1, 10.2, 16.3

— File-AID for IMS 10.1, 10.2, 16.3

— File-AID/RDX 10.1, 10.2, 16.3

— File-AID/Data Solutions 10.1, 10.2, 16.3

— File-AID/EX 5.3 with July 2014 Service Pack, 5.3.1, 5.3.2, 16.3


  Browsers and IDEs

— Microsoft Internet Explorer 8, 9, 10, 11


  These are the minimum requirements for Topaz companion products. Visit FrontLine and select the Topaz product page then select Fixes/Downloads for the latest detailed companion product requirements.

  The File-AID Data Privacy plug-in is not supported in native Eclipse and IBM RDz environments. Topaz must be installed.

  Compuware requires that all current maintenance be applied to the companion products. In order to use the newest features, any specified PTFs must be applied; otherwise, companion products will operate in toleration mode and new features will be disabled.

  File-AID for DB2, File-AID/MVS, File-AID for IMS, and File-AID Common Components make use of APF authorized libraries to be used during the configuration of the Host Communications Interface. The authorized libraries MUST have universal read access.

  File-AID for DB2, File-AID Common Components, File-AID for IMS, and File-AID/MVS are distributed on the File-AID/EP media or via RFN order.

  File-AID Data Privacy is an Eclipse-based plug-in distributed with the Topaz Media or RFN order.

  HCI and CSS are distributed on the Enterprise Common Components (ECC) media.

File-AID Services
Hardware Requirements

  Distributed Systems:

— Processor: 3 GHz minimum*

— Hard Disk: 1 GB (for executables and Derby database)

— Memory: 2 GB minimum,* (4 GB recommended)

* Processor speed and available memory directly impact performance. The faster the processor, and the more memory available, the better your performance will be.

Operating Systems

  Linux (32-bit or 64-bit mode)

— Red Hat Enterprise Linux for Servers 5, 6

  Microsoft Windows (x86, x64 mode)

— 7

— 8.1 Update (KB 2919355)

— 10

— Microsoft Windows Server 2012


  Oracle Java SE 7 (build 60 or higher)

File-AID Rules Engine (FARE) on z/OS UNIX
Hardware Requirements

  Hard Disk: 150 MB (to accommodate the installed files)

Operating Systems

  IBM Mainframe

— IBM z/OS V1.12, 1.13, 2.1, 2.2 (z/OS UNIX for File-AID Rules Engine)


  IBM Java 31-bit SDK V7.0 or higher (only 31-bit Java is supported on z/OS Unix)

File-AID Rules Engine (FARE) for Linux, Unix, and Windows

The File-AID Rules Engine must be installed with the File-AID/EX Execution Server. See the File-AID/EX Release Notes in the Software and Hardware Requirements section under File-AID/EX and File-AID/EX Execution Server.

Supported Database Drivers in File-AID Services and File-AID Rules Engine (FARE)

  jTDS 1.2.5 for accessing MS SQL Server/Sybase databases

— SQL Server 2014 Standard Edition; other editions might be compatible but have not been tested

— SQL Server 2012, 2008, 2005, 2000, 6.5, 7.0 Compliant

— Sybase 15.0.3, 15.5, 15.7

  Oracle Thin JDBC driver - Production

— Oracle JDBC 10.1.0, 10.2.0, 11.1.0, 11.2.0, 12.1.0

  Apache Derby JDBC driver

— Driver intended to support included version of Derby only

  IBM z/OS DB2:

— V10 CM, NFM

— V11 CM, NFM

Discontinued Support

This is the last release to support IBM z/OS V1.

Technical Notes
File-AID Rules Engine (FARE) Requires Mainframe Java 7

When upgrading from a prior version of Data Privacy, the FARE requires the version of Java to be upgraded to Java 7 on the mainframe.

IBM Data Server Driver for JDBC and SQLJ

When using IBM Data Server Driver for JDBC and SQLJ, support for DB2 11 for z/OS requires the following APAR/PTFs:

The following table lists the 4.x and 3.x versions of the IBM Data Server Driver for JDBC and SQLJ and the DB2 11 for z/OS APAR that delivers each version.

IBM Data Server Driver for JDBC and SQLJ version

DB2 11 for z/OS APAR/PTF





Using IBM System z Application Assist Processors (zAAPs) is Recommended

When zAAPs are available at a site, Compuware’s Test Data Privacy solution will take advantage of them when executing via File-AID/Data Solutions, File-AID/RDX, File-AID for DB2, and File-AID for IMS, resulting in greater performance.

Upgrading to Data Privacy 16.03

After upgrading to Data Privacy 16.03, the connected Data Privacy Repositories must be migrated to the 16.03.02 version level before they can be accessed. The repositories can be migrated using the Manage Data Privacy Repositories menu option in the Data Privacy menu. Please contact your Data Privacy administrator if you do not have sufficient access permissions to perform the migration.

File-AID Services, Client, and File-AID Rules Engine (FARE) Compatibility

The Topaz Workbench, File-AID Services, and File-AID Rules Engine must be the same version level. The Topaz Workbench includes the File-AID Data Privacy client. Installation of File-AID Services is independent from that of the Topaz Workbench client and thus can lead to the installed version of one being incompatible with the installed version of the other. Mixed client and server versions could produce error messages or unexpected results.

Note: When updating the z/OS UNIX version of the FARE, if your current FARE was installed in the same directory you originally specified for the transferred installation files, you will need to move the installfare.jar and the files to a different directory before running the installation script again. When updating the FARE, all current files in the target directory are removed and then the new files are added. Therefore, the installfare files must exist in a directory outside the target directory. FARE maintenance is found on Frontline and contains detailed instructions in the readme faremaint file for each supported platform.

Region Size for DPR Disguise

When disguising an extract with File-AID Data Privacy defined Dynamic Privacy Rules (DPR), specify a region size large enough to run Java (REGION=0M is suggested, 200M is the minimum) in your jobcard.

Known Issues
Using IAM Data Sets as Translation Tables

The use of IAM files as translation tables is not supported when applying Dynamic Privacy Rules from File-AID/EX.

Using Translation Table in Oracle Database from a Data Privacy Engine installed in z/OS UNIX

When a job attempts to connect to an Oracle database that contains the translate table, that job will fail with an error message similar to the following:

Method execPrivacyRules failed (RC=8) at line 353 in file EXECDPR.C

This high-level failure message appears due to a number of possible causes. You must run with debug set to FINEST in order to diagnose this cause. The FAERROR output may have the lines shown below.

Throwable occurred: java.sql.SQLException: Internal - Unexpected value
at oracle.jdbc.driver.T4CTTIoauthenticate.processRPA(
at oracle.jdbc.driver.T4CTTIfun.receive(
at oracle.jdbc.driver.T4CTTIfun.doRPC(
at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(
at oracle.jdbc.driver.T4CConnection.logon(
at oracle.jdbc.driver.PhysicalConnection.(
at oracle.jdbc.driver.T4CConnection.(
at oracle.jdbc.driver.T4CDriverExtension.getConnection(
at oracle.jdbc.driver.OracleDriver.connect(
at java.sql.DriverManager.getConnection(
at java.sql.DriverManager.getConnection(

The above output indicates a failure to connect to an assumed Oracle database. Verify whether the test was using a translate table stored on an Oracle database. If so, add the following lines to the Java options dataset member, FAJOPTS:



Adding these two lines will make it possible to run an Oracle translation while the log will be generated in EBCDIC. The user should make a copy of the existing Java options member before making any modification.

Product Documentation

The product installation package does not include the product documentation. The following File-AID Data Privacy documentation is available in electronic format on the product documentation site at Compuware’s customer support website, .

  Release Notes in HTML format

Access the product documentation at the FrontLine documentation site at Compuware GO/FrontLine .

HTML Files

View HTML files with any standard Web browser. Simply click the icon shown in the HTML column on the selected FrontLine Documentation page.

Support Resources

Compuware provides a variety of support resources to make it easy for you to find the information you need.

Compuware Go Customer Support Website

You can access online information for Compuware products via our Compuware Go customer support website at .

Compuware Go provides access to critical information about your Compuware products. You can review frequently asked questions, read or download documentation, access product fixes, or e-mail your questions or comments. The first time you access Compuware Go, you are required to register and obtain a password. Registration is free.

Compuware now offers User Communities, online forums to collaborate, network, and exchange best practices with other Compuware solution users worldwide. To join, go to .

Contacting Customer Support

  USA and Canada: 1-800-538-7822 or 1-313-227-5444.

  All other countries: Contact your local Compuware office. Contact information is available at .


You can report issues via the Quick Link Create & View Support Cases on the Compuware Go home page.

Note: Please report all high-priority issues by telephone.


Compuware Customer Support
Compuware Corporation
One Campus Martius
Detroit, MI 48226-5099

Corporate Website

To access Compuware’s site on the Web, go to . The Compuware site provides a variety of product and support information.

Doc. JAN2017