Release Notes

File-AID Data Privacy 17.02

January 30, 2017

Obtaining the Latest Release Notes

What's New in Release 17.02

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 17.02
January 4, 2017

New functionality has been added for the File-AID Data Privacy solution in three areas:

Additional Information Included in the Disguise Report

A new line has been added to the disguise report to show the layout for the field being disguised. The Layout line will contain the fully qualified field name. The Field line will continue to contain just the field name.

This information is especially valuable when an XREF is used, because the Layout line will include the 01 level name of the field.

Disguise Report Produced as a File

Functionality has been added to the File-AID mainframe products to write the same information which is currently being written to the disguise report to a file. Putting the report information into a file will make finding and filtering of the report information easier, especially when the file being disguised contains a large number of tables and columns.

There are two formats available for the file: fixed format and CSV format. Writing these files is triggered by the presence of the appropriate DD statement within the disguise step:

  When a DPRSTAT1 DD is added to a File-AID Data Privacy job, the disguise report information will be written to a fixed format file.

  When a DPRSTAT2 DD is added to a File-AID Data Privacy job, the disguise report information will be written to a CSV format file.

Execution-time Overrides of Data Element SDIs

Functionality has been added to allow data element Source Data Identifiers (SDIs) to be specified at execution time. Currently, this functionality is only available for mainframe disguise.

Use of the SDI file is controlled by the presence of the DPRSDI DD statement. When this DD statement is included, the SDIs defined in the DPRSDI file will be used instead of the SDIs defined in the Data Privacy Project; these SDIs are a complete replacement for all data elements in the Project. The format of the SDI file can be either XML or JSON; see product documentation for details.

July 1, 2016
Added Functions

File-AID Data Privacy now includes two new functions, CD_IBAN and IS_IBAN, that enable you to determine if a value is an IBAN value and easily generate a check digit for IBAN values.

April 1, 2016
Edit SDI Restriction

Source data identifiers (SDI) are defined for each data element to identify the names of the columns or fields that contain the data for each data element. Each SDI can include a restriction to limit the identification to specific metadata. One of the ways to restrict an SDI is to include the data type and length of the field to be identified.

Prior to this release, the only way to create a restriction for data type and length was to use the drag-and-drop functionality from coverage to locate the field and create an SDI for that field. Also, because metadata is not defined for the global project, there was no way to create a data type and length restriction for SDIs in the global project.

In this release, the data type and length have been split into separate fields, and the values can be edited in both a normal project and in the global project. The restriction will match metadata when the data type and length are the same as the values provided in the metadata. The coverage view should be used to verify that the values entered for data type and length are the correct values for the field.

Compatibility with previous SDIs is provided. Existing SDIs included a single field with the picture clause, and these SDIs will continue to function as before.

Access Field Metadata

Rule logic allows rule execution to process differently based on the logic coded within the rule. In this release, several new functions have been added to provide access to the metadata of the field being processed. These functions include the ability to get each of the following: field name, fully qualified field name, field length, field type, and scale.

Access to these fields expands the flexibility of rule logic to execute differently based on the field being processed. Having access to these values is also very useful when logging messages during rule execution.

Import Project from Previous Release

Prior to Release 17.02, the project import function could only import a project that was exported from the same version. This has created problems because customers often have a more recent version of Data Privacy in their development area than they have deployed for production usage. In this release, the import function supports importing of projects exported from Data Privacy 16.03.02 and later; importing for releases prior to that is not supported.


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 http://frontline.compuware.com/charts/hardware.aspx .

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 V2.1, 2.2 (z/OS UNIX for File-AID Rules Engine)

  Linux

— 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

Languages

  For supported Windows: Oracle Java SE 8

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

Corequisites

  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, 17.2

— File-AID for DB2 10.1, 10.2, 16.3, 17.2

— File-AID for IMS 10.1, 10.2, 16.3, 17.2

— File-AID/RDX 10.1, 10.2, 16.3, 17.2

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

— File-AID/EX 5.3.1, 5.3.2, 16.3

Distributed

  Browsers and IDEs

— Microsoft Internet Explorer 8, 9, 10, 11

Note:

  These are the minimum requirements for Topaz Workbench companion products. Visit FrontLine and select the Topaz Workbench 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 Workbench 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 Workbench 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

Languages

  Oracle Java SE 8

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 V2.1, 2.2 (z/OS UNIX for File-AID Rules Engine)

Languages

  IBM Java 31-bit SDK V8.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 11.1.0.7.0 - Production

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

  Apache Derby JDBC driver 10.6.1.0

— Driver intended to support included version of Derby only

  IBM z/OS DB2:

— V10 CM, NFM

— V11 CM, NFM

— V12


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

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

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

4.15.105

PM96295/UI12420

3.65.102

PM96293/UI12401

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 17.02.00

After upgrading to Data Privacy 17.02.00, the connected Data Privacy Repositories must be migrated to the 17.02.00 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 the 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 installfare.sh 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(T4CTTIoauthenticate.java:516)
at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:295)
at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:186)
at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate.java:390)
at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:356)
at oracle.jdbc.driver.PhysicalConnection.(PhysicalConnection.java:531)
at oracle.jdbc.driver.T4CConnection.(T4CConnection.java:221)
at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:32)
at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:503)
at java.sql.DriverManager.getConnection(DriverManager.java:322)
at java.sql.DriverManager.getConnection(DriverManager.java:358)

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:

-Dfile.encoding=UTF-8

-Dlog.encoding=IBM1047

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.

Rounding Numeric Calculations

A defect related to incorrect rounding of numeric calculations has been fixed. This may cause arithmetic operations within rule logic to produce a different result than with prior releases. Previously, rounding was always rounding down; now the result value will be rounded correctly.


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 FrontLine customer support website, https://go.compuware.com .

  Release Notes in HTML format

  The product manuals in PDF format, which may include a PDX index file and associated folder.

Access the File-AID Data Privacy documentation on the FrontLine documentation site at https://go.compuware.com .

PDF and PDX Files

View and print the PDF files with Adobe Reader version 6.0 or more current. Download a free copy of the reader from Adobe’s website, http://www.adobe.com .

Note: With a few minor exceptions, the provided PDF files comply with the requirements of section 508 of the Rehabilitation Act of 1973.

How to Use a PDX File to Search a Compuware Documentation Set

Compuware creates a PDX file for each release of every mainframe product. The file is available in ZIP format on FrontLine, Compuware’s customer support website, along with this README and a folder containing two data files. By pre-cataloging the content of the product’s PDFs, the PDX file allows you to quickly search across the entire documentation set without having to search each PDF individually.

To use the PDX file for a Compuware product:

1. Go to FrontLine ( https://go.compuware.com ) and navigate to the Documentation page for the desired product.

2. Download all of the PDF files for that product to the same local directory. (The Compuware Installer PDF is only cataloged in the Enterprise Common Components PDX file.)

3. Download the ZIP containing the product’s index file.

4. Extract the contents of the ZIP, sending it to the same directory as the PDF files. Be sure to select “All files/folders in archive” and “Use folder names.”

5. Double click the product’s PDX file (< product >Index.pdx). A Search dialog box will appear with the index pre-selected.

6. Enter a word or phrase to search for. To optimize your search, select one or more qualifiers such as “Whole words only,” then click Search.

Your search results will appear almost instantly, grouped by document. Each document with results can be expanded to show a list of matches, with each match including a brief sample of the context in which it occurred. Every match is hyperlinked to the specific page in the PDF where it was found, enabling you to quickly locate the information you’re looking for.

HTML Format

For your convenience, Compuware also provides the File-AID Data Privacy manuals in the Hypertext Markup Language (HTML) format. View HTML files with any standard web browser. Click the icon 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 FrontLine Customer Support Website

You can access online information for Compuware products via our FrontLine customer support website at https://go.compuware.com .

Compuware FrontLine 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 FrontLine, you are required to register and obtain a password. Registration is free.

Contacting Customer Support

Phone

  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 https://go.compuware.com .

Web

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

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

Mail

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

Corporate Website

To access Compuware’s site on the Web, go to https://www.compuware.com .

The Compuware site provides a variety of product and support information.

Doc. JAN2017