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.
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.
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.
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.
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.
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.
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.
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 .
• 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.
• 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.
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.
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.
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.
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.
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.
Throwable occurred: java.sql.SQLException: Internal - Unexpected value
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.
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.
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 .
Access the File-AID Data Privacy documentation on the FrontLine documentation site at https://go.compuware.com .
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 .
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.
1. Go to FrontLine ( https://go.compuware.com ) and navigate to the Documentation page for the desired product.
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.
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.
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.
• All other countries: Contact your local Compuware office. Contact information is available at https://go.compuware.com .
To access Compuware’s site on the Web, go to https://www.compuware.com .