File-AID Release Notes

Release 17.02

October 2, 2017

Latest Release Notes

What’s New

File-AID Installation

File-AID/MVS

File-AID/Data Solutions

File-AID/RDX

File-AID for DB2

File-AID for IMS

File-AID/EX Enterprise Edition

October 2, 2017

October 2, 2017

 

 

 

October 2, 2017

 

June 28, 2017

 

 

 

 

 

 

April 3, 2017

April 3, 2017

April 3, 2017

April 3, 2017

 

 

 

January 4, 2017

January 4, 2017

January 4, 2017

January 4, 2017

January 4, 2017

January 4, 2017

 

October 3, 2016

October 3, 2016

 

October 3, 2016

October 3, 2016

 

October 3, 2016

June 28, 2016

June 28, 2016

 

June 28, 2016

June 28, 2016

 

 

April 1, 2016

April 1, 2016

April 1, 2016

April 1, 2016

April 1, 2016

April 1, 2016

April 1, 2016

 

 

 

 

 

 

 

File-AID Maintenance Support

Software and Hardware Requirements

Discontinued Support

Technical Notes

Known Issues

Product Documentation

Support Resources

 

The File-AID installation media includes the z/OS versions of all Compuware File-AID products. All products in the File-AID installation media are on the same release level. Compuware recommends that you install and activate all of your licensed File-AID mainframe products at the same time to avoid compatibility issues between different release levels.

IMPORTANT:

Follow the instructions in the File-AID Installation and Configuration Guide in detail, as the installation and configuration of File-AID products have changed from previous releases.

Note: All FMIDs of your selected File-AID product(s) plus the FMID for File-AID Common Components need to be received, applied, and accepted.

  If you don’t install Japanese language modules, FMIDs for Japanese language modules don’t need to be received, applied, and accepted.

  If you do install Japanese language modules, FMIDs for Japanese language modules need to be received, applied, and accepted in addition to all FMIDs for non-Japanese language modules.

 

Latest Release Notes

These Release Notes may have been revised. For the latest version, go to Compuware's FrontLine customer support website at https://go.compuware.com . 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 and click Go. 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

File-AID Installation
October 2, 2017

The following enhancements have been introduced to File-AID Release 17.02 via Cumulative Maintenance File-AID_R17_Q417:

PARMLIB Processing

Compuware has enhanced the Compuware PARMLIB parameter processing, including centralized parameter validation. Additionally, some parameters for the Compuware products were changed to reduce their complexity and make them easier to understand and configure. With this Cumulative Maintenance these changes have been incorporated into the sample parameter members that are supplied in the target sample library.

Enterprise Common Components (ECC) PTF CXS269A provides a parameter migration utility to assist with updating any existing Compuware parameter members at your site. Please refer to the Enterprise Common Components Installation and Customization Guide for more information about using this utility.

Sample DB2 Environment PARMLIB Members FADE00 and FADEALL
DB2_SUBSYSTEM_DESCRIPTION

New parameter DB2_SUBSYSTEM_DESCRIPTION has been added to the sample DB2 Environment PARMLIB members FADE00 and FADEALL to add a description for the DB2 Subsystem. This optional description is helpful when users need to select a DB2 Subsystem in File-AID for DB2 and File-AID/RDX.

Sample File-AID Common Components PARMLIB Member FACMALL
DISALLOW_ANY_HLQ_WILDCARD

New parameter DISALLOW_ANY_HLQ_WILDCARD has been added to the sample File-AID Common Components PARMLIB member FACMALL. When set to Y (Yes), pattern characters (*, +, %, etc.) in the high level qualifier of a dataset for File-AID/MVS options 3.4 and 3.7 are not allowed. Default is N (No).

Revised File-AID Installation Documentation

The previous File-AID Single Install Image Installation and Configuration Guide has been revised and divided into two separate guides:

File-AID Installation and Configuration Guide

This comprehensive guide leads you through installing/updating, configuring, and deploying the z/OS versions of Compuware File-AID products.

File-AID Advanced Configuration Guide

This guide supplements the File-AID Installation and Configuration Guide and provides additional and more detailed information for configuring the z/OS versions of Compuware File-AID products.

June 28, 2017

The following enhancements have been introduced to File-AID Release 17.02 via Cumulative Maintenance File-AID_R17_Q317:

PARMLIB Processing
Sample Core and ALL PARMLIB Members

In an effort to simplify the installation process, Compuware has updated the sample PARMLIB members.

Sample PARMLIB members with suffix 00 (FACM00, FADE00, etc.) in hlq .CPWR.MXVJ170.SXVJSAMP provide the core parameters required for File-AID and should be used as a skeleton for parameters for your particular installation.

Sample PARMLIB members with suffix ALL (FACMALL, FADEALL, etc.) include all available parameters. If your site requires non-core parameters, you only need to copy those individual parameters to your site PARMLIB member that require non-default parameter values.

The updated XVJPARSE parser program allows you to still use your existing PARMLIB members that have parameters no longer listed in the provided sample PARMLIB members FA xx 00 and FA xx ALL.

Refresh your site’s File-AID PARMLIB members and XVJPARSE parser program.

April 3, 2017

The following enhancements have been introduced to File-AID Release 17.02 via Cumulative Maintenance File-AID_R17_Q217:

PARMLIB Processing
PARMLIB Members and XVJPARSE Parser

Compuware has updated the sample PARMLIB members and the XVJPARSE parser program. The parameter keywords are no longer restricted to 8 characters and the sample PARMLIB members now present the longer, more descriptive keywords, for example, the short keyword HSMOPT has been replaced with its long name DISPLAY_ARCHIVED_MIGRATED_DATASET_SCREEN.

The updated XVJPARSE parser program now handles both short and long keywords, which allows you to still use your existing PARMLIB members that have short keywords.

The updated sample JCL (XVJCNV) in the sample library SXVJSAMP converts PARMLIB Load Modules created with File-AID Release 10.01 through 16.03 into PARMLIB Members for File-AID Release 17.02 with the longer, more descriptive keywords.

The new sample JCL (XVJCNVP) in the sample library SXVJSAMP converts your earlier File-AID Release 17.02 PARMLIB members to have the longer, more descriptive keywords.

Refresh your site’s File-AID PARMLIB members and XVJPARSE to support the long name parameters.

Sample DB2 Environment PARMLIB FADE00
DB2_TCPIP_PORT

New parameter DB2_TCPIP_PORT has been added to the sample DB2 Environment PARMLIB FADE00 to identify the Port number for TCP/IP communication with DB2. Refresh your site’s XVJPARSE parser program with the updated one to support this new long name parameter.

Sample File-AID for IMS PARMLIB FAIX00
MFS_END_MOD

The File-AID for IMS /DC specific MFS_END_MOD parameter has been added to the sample PARMLIB member FAIX00. It allows you to specify the MFS MOD name that you want formatted upon exit. Leave blank if MOD is not to be formatted upon exit.

January 4, 2017

The following enhancements have been introduced to File-AID Release 17.02 via Cumulative Maintenance File-AID_R17_Q117:

Sample IMS Environment PARMLIB FAIE00

New parameters CTLGIND and CTLGBOOT have been added to the IMS Environment PARMLIB FAIE00 to support Topaz Workbench Edit/Browse access to IMS systems running with IMS management of ACBs:

   CTLGIND indicates whether this IMS system is using IMS Management of ACBs. Default is N (No).
Y (Yes) specifies that this IMS system is using IMS Management of ACBs.

   CTLGBOOT specify the prefix of the IMS Boot Strap Dataset. For example, if the Boot Strap dataset is IMSTEST.DFSCD000.BSDS, specify IMSTEST.DFSCD000 . Default is blank (no prefix specified).

October 3, 2016

The following have been introduced to File-AID Release 17.02 via Cumulative Maintenance FK170_T170903:

PARMLIB Processing
PARMLIB Members and XVJPARSE Parser

Compuware has updated the sample PARMLIB members and the XVJPARSE parser program. You must refresh your site’s File-AID PARMLIB members and XVJPARSE.

PARMLIB Member Suffixes

The restriction that all File-AID PARMLIB member suffixes had to be the same has been removed. If you decide to use a suffix other than the default, use the XVJSFXA PROC found in the SXVJSAMP library to create an XVJSFX load module that identifies the new suffixes for the File-AID PARMLIB members.

File-AID for DB2 Sample PARMLIB FAFD00
MAXLOB

The verification of the MAXLOB parameter (Maximum byte size LOB data retrieved in BROWSE or EDIT) has been changed to only allow even values (2-4096). The default (4096) remains unchanged.

Training Files

Compuware provides sample JCL to create a complete master set of MVS (XVJTRNM) and (XVJTRND) training files that can be used for all File-AID products. Five sample CLISTs (UDACOPY, XFACOPY, XFDCOPY, XIXCOPY, and XFRCOPY) need to be tailored to your site requirements to copy File-AID master training files to individual users for training. These samples are located in the sample library, hlq .CPWR.MXVJ170.SXVJSAMP.

June 28, 2016

The following enhancements have been introduced to File-AID Release 17.02 via Cumulative Maintenance FK170_T170902:

PARMLIB Conversion Utility
Conversion Output with Comments

The conversion utility provided in sample JCL (XVJCNV) in the sample library SXVJSAMP has been updated. The conversion output now includes comments describing the parameters.

Data Privacy Environment
Parameter TCPIPNME

The new Parameter TCPIPNME has been added to the sample PARMLIB member FADP00. TCPIPNME allows you to specify TCP/IP stack information other than the default TCP/IP stack. If TCPIPNME is blank, the default TCP/IP stack name will be used.

April 1, 2016

The following enhancements have been introduced to the initial File-AID Release 17.02:

Compuware Simple Installation for Mainframe Products

Compuware’s Simple Installation fundamentally changes the way Compuware mainframe products are installed and configured. Simple Installation streamlines the process into logical task flows and checklists, as suggested through numerous customer feedback initiatives. Compuware delivers the first phase of Simple Installation with the introduction of PARMLIB-enabled solutions in Release 17.02 of our mainframe products.

The next phases of Simple Installation are planned and will provide more features to further reduce the time, resources, and effort needed to install and configure Compuware solutions across one or many LPAR instances.

CMSC PARMLIB Enablement

Each mainframe product now uses the Compuware Mainframe Services Controller (CMSC) PARMLIB facility, which gives many advantages over previous customization methods. Some of these features include:

  Similarity to the current IBM z/OS PARMLIB, which is readily intuitive and familiar to many z/OS software installers.

  Simple, consistent method to configure human readable parameters for Compuware products using a text editor.

  Use of System Symbolics in PARMLIB members allows for maximum flexibility.

  Easy deployment of installed software to other LPARs and sysplexes by simply copying the current PARMLIB file.

  Migration to newer releases by simply copying the current PARMLIB file, thereby shortcutting or eliminating future repetitive and/or lengthy tasks (such as, compiling or executing configuration dialogs).

Introducing PARMLIB Services for File-AID

In an effort to standardize the installation and configuration processes for all Compuware mainframe products, the File-AID configuration now utilizes parameter libraries (PARMLIB).

This requires Enterprise Common Components (ECC) Release 17.02 or Release 16.05 with all current maintenance applied.

Compuware recommends to store your site’s PARMLIB members in a common library. A copy of your parameter library must reside in the //CWPARM concatenation of the Compuware Mainframe Services Controller (CMSC).

The Compuware Mainframe Services Controller (CMSC) address space is a centralized facility providing the common parameter library services. It provides two basic functions in relation to parameters: storage and retrieval. Users will modify a human readable PARMLIB member and issue a modify command to the CMSC to store this new set of parameters into a common memory object that can be accessed regardless of the CMSC being active. When the CMSC is initialized all PARMLIB members will be loaded into a common memory object. Refer to the Enterprise Common Components Installation and Customization Guide for Release 16.05 for further information on CMSC.

  1. File-AID product PARMLIB members 

Component

Component PARMLIB Name Prefix

Default PARMLIB Member

Shared configuration data

 

File-AID Common Components (required for all products)

FACM

FACM00

DB2 subsystem environment

FADE

FADE00

IMS environment

FAIE

FAIE00

Data Privacy environment

FADP

FADP00

Individual product configuration data

 

File-AID/MVS

FAMV

FAMV00

File-AID/Data Solutions

FADA

FADA00

File-AID for DB2

FAFD

FAFD00

File-AID for IMS 1

FAIX

FAIX00

File-AID/RDX

FAFR

FAFR00

The File-AID Common Components PARMLIB member is required for the installation and execution of all Compuware Mainframe File-AID products as well as the File-AID Eclipse and File-AID Data Privacy components of the Topaz Workbench. Sample PARMLIB members are provided that sites can modify to their requirements during configuration.

Conversion Utility XVJCNV

File-AID provides sample JCL (XVJCNV) in the sample library SXVJSAMP that converts PARMLIB Load Modules created with File-AID Release 10.01 through 16.03 into PARMLIB Members for File-AID Release 17.02.


File-AID/MVS
October 2, 2017

The following enhancements have been introduced to File-AID Release 17.02 via Cumulative Maintenance File-AID_R17_Q417:

Library Utility (Option 3.1)
Load Module Directory and Linkage Information

When creating a CSV file, Library Utility Options A, Map CSECTs in address order, and N, Map CSECTs in name order, will now include Load Library Directory Information and Link Edit Attributes.

Library Utility Option I, Display directory entry of member, now allows for the creation of a CSV file.

April 3, 2017

The following enhancements have been introduced to File-AID Release 17.02 via Cumulative Maintenance File-AID_R17_Q217:

Browse and Edit
Browse and Edit in 64-bit Memory Mode

These additional commands for Browse and Edit in 64-bit Memory Mode have been added:

-- EXCLUDE primary command is available in all display modes (CHAR, FMT, VFMT, UNFMT) and supports all file types except for KSDS Browse when Display line number in BROWSE is set to NO .

-- F[n] First line command

-- L[n] Last line command

-- S Show line command

-- X[n], XX Exclude line command

File-AID/Batch
Audit Function APRINT Allows Multiple $$DDxx

The restriction that the audit trail dataset must be specified as $$DD01 when used with APRINT has been removed. You can now specify multiple, unique, $$DDxx audit trail datasets when used with APRINT. The report is written to the SYSLIST DD.

Member Name Length Parameter MEMNAMELENGTH (MNL)

The MEMNAMELENGTH parameter limits the member selection from a PDS to members that have a name length equal to the value given for MEMNAMELENGTH. MNL can be used with or without a mask.

January 4, 2017

The following enhancements have been introduced to File-AID Release 17.02 via Cumulative Maintenance File-AID_R17_Q117:

Processing Parameters (Option 0.4)
Specify VSAM KSDS Processing Options

The new processing options Display line number in BROWSE and Display line number in EDIT only apply to processing VSAM KSDS files. The default NO for either Browse and Edit with line numbers indicates that File-AID/MVS will access your VSAM KSDS dataset in 64-bit memory mode. When Display line number in BROWSE is NO , larger files require less memory in 64-bit than 31-bit memory mode. When Display line number in EDIT is NO , only the records that are viewed and/or searched are loaded into memory. If the display of line numbers is important, you may set this option to YES and File-AID/MVS attempts to use 31-bit memory first and load all records into memory. When either is set to YES , and when 31-bit memory is exhausted, then File-AID/MVS will switch to 64-bit memory mode.

Edit
Edit in 64-bit Memory Mode

These additional commands for Edit in 64-bit Memory Mode have been added:

-- PAD primary command

-- ([n], (([n] Shift Left line command

-- )[n], ))[n] Shift Right line command

VSAM Utility (Option 3.5)
Formatted Batch

The new processing option F (Formatted Batch) for VSAM Utility option “BLANK - Display dataset information” produces a report that uses the same layout as the online report.

File-AID/Batch
NEWMEM/NEWMEMS

The NEWMEM and NEWMEMS parameters now allow specifying a load library PDS or PDSE for a COPY function.

October 3, 2016

The following enhancements have been introduced to File-AID Release 17.02 via Cumulative Maintenance FK170_T170903:

Browse and Edit
LR Primary Command

The LR (Locate Record) primary command is now also available in Unformatted (UNFMT) Browse.

Library Utility (Option 3.1)
COBOL and PL/I Compiler Options for Load Libraries

Library Utility Options A, Map CSECTs in address order, and N, Map CSECTs in name order, now allow you to list the compiler options for load modules that have CSECTs compiled with any IBM COBOL compiler (excluding OS/VS COBOL) or any IBM Enterprise PL/I for z/OS and OS/390 compiler starting with Release 3.1. Use the compiler options listing as reference when re-compiling COBOL or PL/I modules.

Copy Utility (Option 3.3)
Generations Support for Version 2 PDSE

When copying from a Version 2 PDSE with member generations, Copy recognizes and copies all selected member generations, if you specify a single Version 2 PDSE in the “FROM” Dataset name field and a NEW “TO” Dataset. Member generation is only supported when you do not specify:

-- I/O exits

-- Selection criteria

-- Batch processing

All other Copy options only recognize the current member (0 generation).

June 28, 2016

The following enhancements have been introduced to File-AID Release 17.02 via Cumulative Maintenance FK170_T170902:

Library Utility (Option 3.1)
COBOL Compiler Options for Load Libraries

Library Utility Options A, Map CSECTs in address order, and N, Map CSECTs in name order, now allow you to list the compiler options for load modules compiled with Enterprise COBOL Release 3.1 or newer. Use as reference when re-compiling the load modules.

CSECT Map Information Output to CSV File

For Batch processing only, Library Utility Options A, Map CSECTs in address order, and N, Map CSECTs in name order, now allow you to also direct the report output to a CSV (Comma Separated Value) file. The CSV contains all the CSECT Map information, including the compiler options for each load module selected.

Search/Update Utility (Option 3.6)
Generations Support for Version 2 PDSE in Option B, Browse

When specifying a single Version 2 PDSE, in the Dataset name field for Search/Update Utility Option B, Browse, you can specify how many member generations to include in the search in the PDS Processing Option screen.

April 1, 2016

The following enhancements have been introduced to the initial File-AID Release 17.02:

Browse and Edit

The following enhancements have been implemented for the File-AID/MVS Browse and Edit functions (Option 1 and 2):

  Additional Primary Commands for Edit and Browse in 64-bit Memory Mode:

-- COLS

-- COPY

-- CUT

-- DELETE

-- PASTE

-- PROTECT for KSDS files in formatted (FMT) mode

Miscellaneous

The following miscellaneous enhancements have been implemented:

  Support for IBM Enterprise COBOL for z/OS 6.1. Enterprise COBOL 6.1 is supported at the current feature level of previous COBOL releases without exploiting new functionality.


File-AID/Data Solutions
April 3, 2017

The following enhancement has been introduced to File-AID Release 17.02 via Cumulative Maintenance File-AID_R17_Q217:

File-AID/Batch
Audit Function APRINT Allows Multiple $$DDxx

The restriction that the audit trail dataset must be specified as $$DD01 when used with APRINT has been removed. You can now specify multiple, unique, $$DD xx audit trail datasets when used with APRINT. The report is written to the SYSLIST DD.

January 4, 2017

The following enhancements have been introduced to File-AID Release 17.02 via Cumulative Maintenance File-AID_R17_Q117:

Data Encryption
Encryption/Decryption Exit ENCRYPTC

The new Encryption/Decryption Exit ENCRYPTC is the same as the ENCRYPT exit, except that it treats a display numeric data field, with a length of 18 bytes or less, as if the field was defined as a character field.

Data Privacy
Optional Data Privacy Report Output Written to a File

If you want the Data Privacy Report information written to a fixed layout sequential file and/or to a CSV (Comma Separated Values) file, manually add the appropriate DD statement to the File-AID Data Privacy job:

  DPRSTAT1 DD for a Fixed Layout Sequential file

  DPRSTAT2 DD for a CSV (Comma Separated Values) file

This functionality requires File-AID Data Privacy Release 17.2.3 or newer.

Optional Source Data Identifiers (SDIs) Override During Execution

If you want to replace, during execution of a DPR project, Source Data Identifiers (SDIs) defined in the File-AID Data Privacy project, manually add the following DD statement to the JCL:

//DPRSDI   DD   DISP=SHR,DSN= u.data.mysdis

where the existing dataset u.data.mysdis contains the definitions of SDIs that will be used for this execution.

If the DPRSDI DD is defined in JCL, all SDIs defined in the project will be ignored and replaced with definitions provided in the override dataset.

This functionality requires File-AID Data Privacy Release 17.2.3 or newer.

April 1, 2016

The following File-AID product enhancements have been introduced to File-AID Release 17.02:

Data Privacy
XVJPRINT Execution Log Output

File-AID Data Privacy jobs now write execution information to XVJPRINT DD (instead of SYSPRINT DD). If XVJPRINT DD does not exist in your JCL, File-AID will dynamically allocate XVJPRINT.

If you want the execution log output sent to a file, point the XVJPRINT DD to a file (instead of SYSOUT=*). This file must be allocated with RECFM=FBA, LRECL=133.

Miscellaneous

The following miscellaneous enhancement has been implemented:


File-AID/RDX
April 3, 2017

The following enhancements have been introduced to File-AID Release 17.02 via Cumulative Maintenance File-AID_R17_Q217:

Load
Generate Control Datasets for Objects with Zero Rows Extracted

The File-AID/RDX Load JCL now creates Load Control Table (LCT) datasets and SORT datasets for objects which have zero rows extracted when Generate Control Datasets in the Load Profile function is set to Y es.

Existing Load JCL with IDENTITY Columns

Submitting existing load JCL with load control tables that include IDENTITY columns no longer requires column remapping when additional columns have been added to the target table.

Support for ICETOOL Sort Utility

The File-AID/RDX Load JCL now supports the ICETOOL utility for sorting when Use ICETOOL for Batch Sorts in the Profile function is set to Y es.

January 4, 2017

The following enhancements have been introduced to File-AID Release 17.02 via Cumulative Maintenance File-AID_R17_Q117:

Data Privacy
Optional Data Privacy Report Output Written to a File

If you want the Data Privacy Report information written to a fixed layout sequential file and/or to a CSV (Comma Separated Values) file, manually add the appropriate DD statement to the File-AID Data Privacy job:

  DPRSTAT1 DD for a Fixed Layout Sequential file

  DPRSTAT2 DD for a CSV (Comma Separated Values) file

This functionality requires File-AID Data Privacy Release 17.2.3 or newer.

Optional Source Data Identifiers (SDIs) Override During Execution

If you want to replace, during execution of a DPR project, Source Data Identifiers (SDIs) defined in the File-AID Data Privacy project, manually add the following DD statement to the JCL:

//DPRSDI   DD   DISP=SHR,DSN= u.data.mysdis

where the existing dataset u.data.mysdis contains the definitions of SDIs that will be used for this execution.

If the DPRSDI DD is defined in JCL, all SDIs defined in the project will be ignored and replaced with definitions provided in the override dataset.

This functionality requires File-AID Data Privacy Release 17.2.3 or newer.

October 3, 2016

The following enhancements have been introduced to File-AID Release 17.02 via Cumulative Maintenance FK170_T170903:

Extract
Batch Extract Checkpoint and Resumption

File-AID/RDX provides the ability to identify a checkpoint in an extract request that will stop the execution of the extract in a controlled manner. Stop a checkpoint enabled extract at a pre-determined checkpoint or any time during execution with an Operator command. After the controlled stop, resume the extract execution from the checkpoint. Use this functionality when you anticipate a long running extract that might not complete within your site’s constraints or when executing complex related extracts.

June 28, 2016

The following enhancements have been introduced to File-AID Release 17.02 via Cumulative Maintenance FK170_T170902:

Extract
Record Layout Option FA COBOL

When requesting File-AID/RDX to create record layouts for DB2 objects, the new Language Option 3, FA COBOL creates a File-AID COBOL layout with special type VAR for DB2 column type VCHAR or VC. For example, when the FIRSTNME column is defined to DB2 as VARCHAR(12), with Option 3, FA COBOL it will be generated as 10 FIRSTNME PIC X(12) VAR. Use option 3, FA COBOL when you need to define disguise criteria for DB2 tables with column type VARCHAR.

April 1, 2016

The following File-AID product enhancements have been introduced to File-AID Release 17.02:

Extract
Support for Topaz Extract Visualizer

For extracts, you can request File-AID/RDX to create a Topaz Extract Visualizer file (also known as the File-AID/RDX Extract Mainframe Trace file in Topaz Workbench). File-AID/RDX will capture statistics (TPT trace) during extract job execution and save them along with the extract request information to the Topaz Extract Visualizer file. The Data Visualizer component of the Topaz Workbench Release 17.02 can use this file to produce a graphical display with detailed information about extract processing. The insight provided by the Topaz Extract Visualizer allows you to better understand complex related extracts, extract requests, and relationship repositories. Users will benefit by developing higher quality extracts, enhanced understanding of troublesome extract areas, and quicker problem resolution if tuning is needed.

Data Privacy
XVJPRINT Execution Log Output

File-AID Data Privacy jobs now write execution information to XVJPRINT DD (instead of SYSPRINT DD). If XVJPRINT DD does not exist in your JCL, File-AID will dynamically allocate XVJPRINT.

If you want the execution log output sent to a file, point the XVJPRINT DD to a file (instead of SYSOUT=*). This file must be allocated with RECFM=FBA, LRECL=133.

Miscellaneous
File-AID/RDX PARMLIB Member FAFR00

Changes in the PARMLIB Member FAFR00 for File-AID/RDX include:

  Parameter EXIT (Encryption Exit) has been removed.

  Parameter REQCONV (Convert Pre V4 extract request file) has been removed.


File-AID for DB2
January 4, 2017

The following enhancements have been introduced to File-AID Release 17.02 via Cumulative Maintenance File-AID_R17_Q117:

Data Privacy
Optional Data Privacy Report Output Written to a File

If you want the Data Privacy Report information written to a fixed layout sequential file and/or to a CSV (Comma Separated Values) file, manually add the appropriate DD statement to the File-AID Data Privacy job:

  DPRSTAT1 DD for a Fixed Layout Sequential file

  DPRSTAT2 DD for a CSV (Comma Separated Values) file

This functionality requires File-AID Data Privacy Release 17.2.3 or newer.

Optional Source Data Identifiers (SDIs) Override During Execution

If you want to replace, during execution of a DPR project, Source Data Identifiers (SDIs) defined in the File-AID Data Privacy project, manually add the following DD statement to the JCL:

//DPRSDI   DD   DISP=SHR,DSN= u.data.mysdis

where the existing dataset u.data.mysdis contains the definitions of SDIs that will be used for this execution.

If the DPRSDI DD is defined in JCL, all SDIs defined in the project will be ignored and replaced with definitions provided in the override dataset.

This functionality requires File-AID Data Privacy Release 17.2.3 or newer.

October 3, 2016

The following enhancements have been introduced to File-AID Release 17.02 via Cumulative Maintenance FK170_T170903:

Browse/Edit
Support for DBCLOB Data Types

Tables with DBCLOB data types can now be browsed and edited in similar fashion as CLOB and BLOB data types.

XLOB Edit Support in Audit Trail

In an audit trail report with XLOB update, instead of showing the before and after images of the LOB column, the report shows the message <<< UPDATED BY XLOB PROCESS >>> and lists the saved before and after XLOB audit trail file names.

June 28, 2016

The following enhancements have been introduced to File-AID Release 17.02 via Cumulative Maintenance FK170_T170902:

Browse/Edit
XLOB Command for BLOB and CLOB Data Types

Column Data with a length exceeding the MAXLOB parameter value is protected, but can be edited with the XLOB primary command when in EDIT ROW mode. The XLOB command retrieves the entire data record of the target LOB column (CLOB or BLOB) into a temporary work file and starts a File-AID/MVS edit session to edit the work file data. Upon exiting the File-AID/MVS edit session, the target LOB column is updated with the work file contents.

The XLOB SET command displays the XLOB Work File Allocation Parameters window where you can change the work file allocation attributes.

Miscellaneous
Archive Table Type ‘R’

In File-AID for DB2 table lists, Archive Table Type ‘R’ is identified as Type ARCHV. The following File-AID for DB2 functions support Archive Tables:

-- Option 1, Browse

-- Option 2, Edit

-- Option 3.3, Copy Rows Between Tables

-- Option 3.4, Object List Utility

-- Option 3.7.3, Extract from a Table to a dataset

-- Option 3.7.4, Load from a dataset to a Table

-- Option 3.7.5, Extract and Load

-- Option 5.1, Print table Data

April 1, 2016

The following File-AID product enhancements have been introduced to File-AID Release 17.02:

Data Privacy
XVJPRINT Execution Log Output

File-AID Data Privacy jobs now write execution information to XVJPRINT DD (instead of SYSPRINT DD). If XVJPRINT DD does not exist in your JCL, File-AID will dynamically allocate XVJPRINT.

If you want the execution log output sent to a file, point the XVJPRINT DD to a file (instead of SYSOUT=*). This file must be allocated with RECFM=FBA, LRECL=133.


File-AID for IMS
October 2, 2017

The following enhancements have been introduced to File-AID Release 17.02 via Cumulative Maintenance File-AID_R17_Q417:

File-AID for IMS /ISPF
Support for IMS managed ACB

File-AID for IMS continues to provide support for the IBM IMS Catalog. File-AID for IMS now provides IMS Managed ACB support in Browse, Edit, Extract, Load, FLEX and Topaz Workbench File-AID Data Editor.

January 4, 2017

The following enhancements have been introduced to File-AID Release 17.02 via Cumulative Maintenance File-AID_R17_Q117:

File-AID for IMS /ISPF Data Privacy
Optional Data Privacy Report Output Written to a File

If you want the Data Privacy Report information written to a fixed layout sequential file and/or to a CSV (Comma Separated Values) file, manually add the appropriate DD statement to the File-AID Data Privacy job:

  DPRSTAT1 DD for a Fixed Layout Sequential file

  DPRSTAT2 DD for a CSV (Comma Separated Values) file

This functionality requires File-AID Data Privacy Release 17.2.3 or newer.

Optional Source Data Identifiers (SDIs) Override During Execution

If you want to replace, during execution of a DPR project, Source Data Identifiers (SDIs) defined in the File-AID Data Privacy project, manually add the following DD statement to the JCL:

//DPRSDI   DD   DISP=SHR,DSN= u.data.mysdis

where the existing dataset u.data.mysdis contains the definitions of SDIs that will be used for this execution.

If the DPRSDI DD is defined in JCL, all SDIs defined in the project will be ignored and replaced with definitions provided in the override dataset.

This functionality requires File-AID Data Privacy Release 17.2.3 or newer.

File-AID for IMS /CICS and File-AID for IMS /DC
Primary Options Menu

The USERID and PASSWORD fields have been removed from the Primary Options menus of File-AID for IMS /CICS and File-AID for IMS /DC.

Security Exits

The USERID and PASSWORD fields have been removed from the sample security exits for File-AID for IMS /CICS and File-AID for IMS /DC. New Assembler security exits have been added for File-AID for IMS /CICS (XIXCSCXA) and File-AID for IMS /DC XIXDSCXA).

Miscellaneous
Topaz Workbench Support for IMS Systems Running with IMS Management of ACBs

If the IMS system is running with IMS management of ACBs, Topaz Workbench supports Edit/Browse access to the databases on that IMS system. Please refer to the Topaz Workbench Installation Guide for information about HCI and CSS TP configuration.

Requirements:

-- IMS V14 with APAR PI68811

-- The IMS RESLIB must be added to the STEPLIB for the Started Task.

-- In the IMS Environment PARMLIB FAIE nnnn , new parameters CTLGIND and CTLGBOOT need to be specified:

   CTLGIND indicates whether this IMS system is using IMS Management of ACBs. Default is N (No).
Y (Yes) specifies that this IMS system is using IMS Management of ACBs.

   CTLGBOOT specify the prefix of the IMS Boot Strap Dataset. For example, if the Boot Strap dataset is IMSTEST.DFSCD000.BSDS, specify IMSTEST.DFSCD000 . Default is blank (no prefix specified).

April 1, 2016

The following File-AID product enhancements have been introduced to the initial File-AID Release 17.02:

File-AID for IMS /FLEX
Multiple EXTRACTx Subcommands

If multiple EXTRACT x subcommands are present in one SELECT and the EXTRACT x DD statements specify the same PDS dataset, that dataset must be a PDSE.

Extract
Key Value With Both INPUT And Selection Value

It is now possible to define selection criteria on a key value using both INPUT statements and selection criteria with an "EQ" or "=" relational operator. The key value to be used will be constructed from those portions of the key that come from the key input file and those portions that are defined to have a particular value.

Data Privacy
XVJPRINT Execution Log Output

File-AID Data Privacy jobs now write execution information to XVJPRINT DD (instead of SYSPRINT DD). If XVJPRINT DD does not exist in your JCL, File-AID will dynamically allocate XVJPRINT.

If you want the execution log output sent to a file, point the XVJPRINT DD to a file (instead of SYSOUT=*). This file must be allocated with RECFM=FBA, LRECL=133.

Miscellaneous

  User Parameter Options 0.I Information and 0.A Administration have been removed from the Option 0 Parameters Selection Menu.

  Type N (Database Dataset Names) security exit is no longer supported.


File-AID/EX Enterprise Edition

File-AID/EX Enterprise Edition is an optional addition to File-AID/EX (a Windows based version of File-AID for working with distributed LUW data) and includes File-AID/EX Executive.

October 3, 2016

The following enhancements have been introduced to File-AID Release 17.02 via Cumulative Maintenance FK170_T170903:

Support for IBM Authentication Methods

To provide a higher level of authentication assurance for IBM z/OS applications, File-AID/EX Enterprise Edition now supports the use of the following authentication methods:

  IBM Password Phrase Authentication for z/OS

  IBM Multi-Factor Authentication for z/OS

April 1, 2016

The following File-AID product enhancements have been introduced to the initial File-AID Release 17.02:

File-AID/EX Executive

Member XVJXFE in the File-AID sample library (SXVJSAMP) provides sample JCL to configure File-AID/EX Executive.


File-AID Maintenance Support

Compuware is committed to actively supporting its current product releases. Up-to-date product release support and retirement information is available on Compuware’s FrontLine Support - Product Currency Tables page.

 


Software and Hardware Requirements

The Software and Hardware 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 https://go.compuware.com/charts/hardware.aspx .

Hardware Platforms

  Mainframe Systems:

-- z13, z13s

-- zEC12, zBC12

-- z196, z114

-- z10-EC/BC

-- z9-EC/BC

Operating Systems

  IBM z/OS V2.1, 2.2, 2.3

  IBM ISPF for the supported z/OS releases

  LE libraries for the supported z/OS releases

  TSO/E for the supported z/OS releases

Notes:

-- Recommended TSO region sizes for processing:

   File-AID/MVS : Minimum region size of 8 MB. If File-AID/MVS is installed in the LPA, it requires a minimum region size of approximately 6 MB.

   File-AID/Data Solutions : Minimum region size of 8 MB. If File-AID/Data Solutions is installed in the LPA, it requires a minimum region size of approximately 6 MB.

   File-AID/RDX : Minimum region size of 8 MB. In the supplied profiles for batch defaults, the region size is set to 8192K.

   File-AID for DB2 : Minimum region size of 16M.

   File-AID for IMS : Minimum region size of 4 MB

-- If using a smaller region size, use caution when entering wildcards or working with large amounts of data. Increase region size accordingly when processing a large amount of data.

-- IBM's fast data access service of the program management binder uses 64-bit storage rather than a dataspace. Therefore, Compuware recommends changing your system default SMF MEMLIMIT Parameter to NOLIMIT through SMFPRMxx in PARMLIB: MEMLIMIT(NOLIMIT).

-- IBM z/OS Conversion Services need to be activated with the appropriate conversion tables in your system. File-AID uses the conversion services to convert Unicode data. See the z/OS Conversion Services documentation for more information.

-- For File-AID Data Privacy jobs using Dynamic Privacy Rules (DPR), specify a region size large enough to run Java (REGION=0M is suggested, 200M is the minimum) in your jobcard.

-- For File-AID Data Privacy jobs using Dynamic Privacy Rules (DPR), setting the memory values in the LE STACK option to values lower than the IBM default values can cause a performance degradation. The IBM default is: STACK=((128K,128K,ANYWHERE,KEEP,512K,128K),OVR)

Major Subsystems

  IBM CICS Transaction Server for z/OS V4.1, 4.2, 5.1, 5.2, 5.3, 5.4 (for File-AID products that provide CICS Transactions Server for z/OS support)

  IBM DB2 for z/OS 11.1, 12.1 (for File-AID products that provide IBM DB2 support). IBM DB2 for z/OS 12.1 is supported at the current feature level of previous DB2 releases without exploiting new functionality.

  IBM IMS Transaction and Database Servers V13.1, 14.1 (for File-AID products that provide IBM IMS support)

Languages

  IBM Enterprise COBOL for z/OS V4.2, 5.1, 5.2, 6.1, 6.2. Enterprise COBOL 6.2 is supported at the current feature level of previous COBOL releases without exploiting new functionality.

  IBM Enterprise PL/I for z/OS 4.4, 4.5, 5.1, 5.2. Enterprise PL/I 5.2 is supported at the current feature level of previous PL/I releases without exploiting new functionality.

Corequisites

  Compuware Products and Components:

-- To use Compuware Mainframe Services Controller (CMSC) with:

  Enterprise Common Components (ECC) 17.2, with current maintenance

-- To use File-AID with the Topaz Workbench:

  Please refer to the Topaz Workbench Release Notes for compatibility and requirement information.

  File-AID Data Privacy:
Please refer to the File-AID Data Privacy Release Notes

-- To use File-AID with Xpediter/TSO

  9.3 with PTF XTK0017

  9.4

  16.5

  17.2

-- To use File-AID with Abend-AID:

  12.4 with PTF ACD112Y

  16.5

  17.2

Note: When configuring File-AID support for the Topaz Workbench, you cannot mix versions of File-AID products prior to Release 17.2 with File-AID 17.2 products on the same host and port. Refer to the Topaz Workbench Installation Guide for more details.

ISV Software

  Innovation Access Method (IAM) 9.1 with fixes P910005 and P910167, 9.2 with fix P920095, 9.3 with fix P930003.

Discontinued Support

N/A


Technical Notes
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

File-AID for IMS

File-AID for IMS requires the following IBM APARs:

  PM68699

  PM67324


Known Issues

There are no known issues at this time.


Product Documentation

The product installation package does not include the product documentation. The following File-AID 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 documentation on the FrontLine documentation site at 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 (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.

 


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 http://www.compuware.com .

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

 



1. Includes File-AID for IMS /ISPF, File-AID for IMS /CICS, and File-AID for IMS /DC