New Features

The following new product features and enhancements to existing features are now available in Version 20.0:
The following new features and enhancements to existing features are now available in Version 20.0 of
CA RC/Extract™ for DB2 for z/OS
(CA RC/Extract):
To ensure availability of all features and fixes, you should install all available maintenance. To download and receive maintenance automatically, use CA SMP/E Receive Order. To view a list of available solutions and fixes, select the link for PTFs since GA on the CA Database Management Solutions for DB2 for z/OS Maintenance Grid (login required).
For a list of enhancements for all the
CA Database Management Solutions for DB2 for z/OS
, see New Features. To request product enhancements, contact a product manager or post your request in the "Ideas" section of the Db2 Tools Community.
Integrate with CA Test Data Manager for Data Masking
You can now integrate with CA Test Data Manager to mask data during an extraction while maintaining relational integrity and complex relationships. Data masking hides or obfuscates sensitive and classified data so you can use the protected data during development, testing, and QA processes. Data is extracted and masked while data is in motion by maintaining the relational integrity chain as-is.
To use this feature with CA RC/Extract, you must be a licensed user of CA Test Data Manager 4.8.1 or above. You must also have the CA Test Data Manager Mainframe DB2 Add on 5.4.18 installed.
This feature includes the following new RCX parmlib options:
  • TDM API Db2 plan name
  • TDM API message KSDS file
  • TDM API load library file
This feature also includes a new TDM MAPCSV File field on the Source Definition panel. Use this field to specify the name of the TDM MAPCSV input file to use during the extraction process for masking data. In this file, you specify the columns to be masked. For more information, see Extract Masked Data and Masking Functions for Mainframe in the Test Data Manager documentation.
M504 Deprecated Objects Support
Db2 12 Function Level 504 prevents the creation of the following deprecated objects:
  • Non-UTS segmented and 'classic' partitioned tablespaces
  • tables in a non-UTS segmented and 'classic' partitioned tablespaces
  • Synonyms
  • Hash tables (only supported in CA RC/Query)
CREATE DDL statements for deprecated objects are now generated as follows to enable creation of these objects after activating function level 504:
The SET CURRENT APPLICATION COMPATIBILITY statements are only generated when the current active function level of the Db2 subsystem is at least V12R1M504. The Batch Processor displays the current function level while executing any process. The current level is based on when the CONNECT occurs or is changed.
Column Mapping Support
A new line command M (map) is now available to map the source and target columns while loading data using a target definition. You can map the columns and then change the column mappings, add literals, and add expressions to the columns. This option provides you with more flexibility while loading the data. When you issue the M line command, the new mapping panel (RXPCMAP) is invoked with auto-mapped columns, that are based on column name, data type, and length. The Mapping Expression field in the new panel provides the specifications that are required to direct data during the load process. You can enter literals, column names, and valid IBM expressions and functions. This field is case-sensitive.
This functionality is helpful in the following scenarios:
  • To include the DB2 function as part of the expression for the data types NUMERIC, STRING, DATE, and TIMESTAMP.
  • To assign literal values to a column while loading. You can perform literal mappings on each column when creating a target definition. The literal value is populated in the target column rows during the load.
  • To obtain the column value from the lookup table according to a source column value by using the LOOKUP function. The retrieved value is loaded into the corresponding destination column of the target table.
The mapping expression is propagated to the related tables within the target definition that have referential integrity. Here is a short video that highlights this new feature:

LOOKUP Syntax Enhancement
The LOOKUP syntax has been enhanced with a new parameter (default column). This parameter enables you to specify a default column when extracting data for load functions. When a match is not found for the source column, the value that is specified for
default column
is used for the load. The value for source column is used when
default column
is not specified. New syntax:
<default column>
Here is a short video that highlights the LOOKUP feature:

DB2 12 Support
IBM Db2 12 for z/OS function levels V12R1M100, V12R1M500, and V12R1M
are now supported. For a list of supported function levels, see DB2 Version Support in the CA Database Management Solutions for DB2 for z/OS documentation.
New CREATE VIEW Default Option in OFS Parmlib
A new option O (original), is now provided for the Generate column names with SELECT(*) parameter in the OFS parmlib member. This new option extracts the original view text from SYSIBM.SYSVIEWS and generates a column list when the original CREATE VIEW statement has a column list. The Y (generate) and N (suppress) column list values are still accepted, although O is the new default and recommended setting.
A new health check is also provided.
New Health Check
A new health check, DB2_OFS_CREATE_VIEW, has been added for use with Object Framework Services (OFS). CA_DB2 is the owner. You can use this health check to review the setting of the Generate Column Names with SELECT(*) parameter in the OFS parmlib member.
GENERATE_COLUMN_NAMES_WITH_SELECT(*) controls whether column lists are generated from the original view text in SYSIBM.SYSVIEWS. The health check informs you when you are running with a setting in OFS that may not generate a CREATE VIEW column list that is consistent with the original CREATE VIEW statement. You should review this setting and should adjust as necessary before the DDL is updated.