New Features

The following new product features and enhancements to existing features are now available in Version 20.0 of rcq (CA RC/Query):
dmcrfdfzs20
The following new product features and enhancements to existing features are now available in Version 20.0 of
CA RC/Query® for DB2 for z/OS
(CA RC/Query):
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 "Ideation" section of the Db2 Tools Community.
3
3
Real-Time Statistics Report Enhancements
The following reports have been updated to include columns for real-time statistics:
  • UPDATESIZE, LASTDATCHANGE, GETPAGES, SYS_START, SYS_END, and TRANS_START in the Tablespace Real-Time Statistics Report (TS-RT)
  • GETPAGES, SYS_START, SYS_END, and TRANS_START in the Indexspace Real-Time Statistics Report (IX-RT)
Performance Improvements During Utility Execution
The following performance-related improvements have been made to help reduce the heavy CPU consumption during the utility execution:
  • A new profile option
    Utility Object Count in 1 Step
    is now available. This option specifies how many utility statements to include in each JCL execution step. This option improves system performance when multiple objects are being processed.
  • Utility models have been enhanced to generate LISTDEF and TEMPLATE statements as needed for the following IBM utilities: RUNSTATS, REORG, REBUILD, COPY, UNLOAD, and RECOVER.
  • A REBUILD on a tablespace or table also rebuilds all related indexes.
  • You can now use the RECOVER command from any SYSTEM report to recover from a specific point-in-time (RBA or LOGPOINT).
  • The UNLOAD line command has been enhanced to now generate DSNUTILB to unload data instead of DSNTIAUL. You can also specify the DSNTIAUL line command to unload data using the DSNTIAUL utility.
  • The following model member changes have been made:
    • MJUTLCD (for the CHECK line command) has been replaced by MJUTLCD1.
    • MJUTLIC (for the COPY line command) has been replaced by MJUTLIC1 and MJUTLIC2.
    • MJUTLRC# (for the RECOVER line command) has been replaced by MJUTLRC1 and MJUTLRC2.
    • MJUTLRO (for the REORG line command) has been replaced by MJUTLRO1 and MJUTLRO2.
    • MJUTLUNL is now used for the DSNTIAUL line command to unload data using the DSNTIAUL utility.
    • MJUTLUL is now used for the UNLOAD line command to unload data using DSNUPROC and DSNUTILB.
HDDL Support on Nested Routines
DDL is generated when executing the HDDL line command on any Db2 object that has a relationship with a routine (stored procedure or function (UDF)). All stored procedure and function types are supported. DDL is extracted based on HDDL panel preferences for all referred and related routines. This process lets you create a mirror image of the object on a target subsystem.
For example, when you set R (routines) to Y on the HDDL panel, function and stored procedure DDL is extracted:
  • For a routine that is called by another routine.
  • For a routine that calls another routine.
  • For other related objects (all involved objects). When you execute HDDL on a routine having both CALL statements for different routines, and some SQL statements that refer to other Db2 objects, DDL is generated for all related objects. Related objects include other routines that are called or are calling from the current routine.
For a view or MQT that is calling a routine, DDL is generated for all related objects with routines that are being referred to from the view or MQT.
CREATE PROCEDURE DDL is
not
generated when you execute the HDDL command on an altered procedure.
M504 Deprecated Objects Support
Db2 12 Function Level M504 prevents the creation of the following deprecated objects:
  • Non-UTS segmented and 'classic' partitioned tablespaces
  • Tables in non-UTS segmented and 'classic' partitioned tablespaces
  • Synonyms
  • Hash tables
CREATE DDL statements for deprecated objects are now generated as follows to enable creation of these objects after activating function level M504:
SET CURRENT APPLICATION COMPATIBILITY = 'V12M1M503'; (deprecated object CREATE DDL statements) SET CURRENT APPLICATION COMPATIBILITY = 'V12R1M504';
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. This level is based on when the CONNECT occurs, or is changed, while executing any process.
KEY LABEL Clause Support
You can generate DDL and HDDL that contains the KEY LABEL or NO KEY LABEL clauses in the following CREATE and ALTER statements on DB2 subsystems running at DB2 12 function level M502 (V12R1M502):
  • CREATE STOGROUP
  • CREATE TABLE
  • ALTER STOGROUP
  • ALTER TABLE
The KEYLABEL column from the catalog tables is now displayed in the following reports:
  • Storage Group List (SG-L) and Storage Group Detail (SG-D) (SYSIBM.SYSSTOGROUP)
  • Tablespace List (TS-L) and Tablespace Detail (TS-D) (SYSIBM.SYSTABLESPACE)
  • Table List (T-L) and Table Detail (T-D) (SYSIBM.SYSTABLES)
  • Index List (I-L) and Index Detail (I-D) (SYSIBM.SYSINDEXES)
New Parameter Now Available for the ALL Command
The ALL command has been enhanced to support generating utilities based on the object type. You can specify a line command and a DB2 object type with the ALL command. This command applies the specified line command to all objects of that type in the report. The new syntax follows:
ALL command
object-type
For example, you can generate a Tablespace Table Inquiry report (TS-T) and then specify ALL DDL TS in the command line to generate DDL for only tablespaces in the report. When you press Enter, the DDL command appears as a line command next to only the tablespace objects in the report. Or, you can specify REORG for all indexes in a report by specifying ALL REORG I from the generated report.
I-C Report and Include Keywords and Index on Expression
The column names in the index-column report are now displayed in the correct order. The index columns now display the correct column type that is INCLUDE (INC) or Index on expression (IOE) in the KEYSEQ column, when the report is generated. When the index is based on expression, KEYSEQ has the value of SYSKEYTARGETS.KEYSEQ, and when the index is not based on expression the value of SYSKEYS.COLSEQ is used. The following values are valid:
  • INC (column is part of an index, created with the INCLUDE clause)
  • IOE (index is created based on Expression)
  • Numeric number (sequence number of the column in SYSKEYS.COLSEQ or SYSKEYTARGETS.KEYSEQ based on the index type)
Reduced Empty Spaces Between Columns
The following reports have been enhanced to eliminate white space and to display the most frequently used columns as first and second in the column list:
  • Table Reports: List (T-L), Index (T-I), Column (T-C), View (T-V), Package (T-PK), and Axis (T-A).
  • View Reports: List (V-L), Axis (V-A), Column (V-C), Package (V-PK), and Table (V-T).
  • Index Reports: List (I-L), Column (I-C), and Package (I-PK)
  • Database Reports: List (DB-L), Table (DB-T), Index (DB-I)
  • Tablespace Reports: List (TS-L), Table (TS-T), and Partition List (TS-PL)
  • Plan-List Report (P-L)
  • Package-List Report (P-L)
  • Routine-List Report (R-L)
Existing saved reports might not work after this feature is implemented.
More Detail Reports Updated to Display All Columns of Catalog Data
The following detail reports display basic information from all the columns in the associated DB2 catalog table:
  • Routine Detail Report (R-D) (SYSIBM.SYSROUTINES)
  • Permission and Mask-Detail (PM-D) (SYSIBM.SYSCONTROLS)
  • Table-Detail (T-D) (SYSIBM.SYSTABLES)
  • View-Detail (V-D) (SYSIBM.SYSVIEWS)
  • Index-Detail (I-D) (SYSIBM.SYSINDEXES)
  • Column-Detail (C-D) (SYSIBM.SYSCOLUMNS)
  • System-Image Copy Detail (SY-IC) (SYSIBM.SYSCOPY)
  • Package-Detail (PK-D) (SYSIBM.SYSPACKAGE)
  • Database-Detail(DB-D) (SYSIBM.SYSDATABASE)
  • Plan-Detail (P-D) (SYSIBM.SYSPLAN)
This enhancement improves usability by letting you access and view Db2 catalog information from one report instead of having to navigate to multiple sources to gather this information.
More List Reports Updated to Display All Columns of Catalog Data
The following list reports display basic information from all columns in the associated Db2 catalog table:
  • Routine List Report (R-L) (SYSIBM.SYSROUTINES)
  • Permission and Mask List Report (PM-L) (SYSIBM.SYSCONTROLS)
  • Table Column Report (T-C) (SYSIBM.SYSCOLUMN)
  • Table View Report (T-V) (SYSIBM.SYSVIEWS)
  • Tablespace Partition List Report (TS-PL) (SYSIBM.SYSTABLEPART)
This enhancement improves usability by letting you access and view Db2 catalog information from one report instead of having to navigate to multiple sources to gather this information.
Isolation Level Support
Cursor stability (CS) and uncommitted read (UR) isolation level support has been added for all SELECT queries. CS and UR are supported at the global and user level. This feature prevents queries from locking the tables when the table is being extracted and changed simultaneously by multiple users. The isolation level is appended to the SELECT results using the WITH clause, for example, WITH CS or WITH UR.
For global support, a new RCQ parmlib member is provided in the
hlq
.CDBAPARM data set. You can apply the default setting globally using this member. CS is the global level default. For user level support, a new profile option is provided. The user level setting overrides the global level setting when specified. If left blank (the default), the global level setting is used.
REPAIR Utility Enhancements
The REPAIR utility has been enhanced to support the INSERTVERSIONPAGES and SETCURRENTVERSION clauses of the REPAIR control statement.
  • INSERTVERSIONPAGES
    Inserts missing version zero system pages to ensure that the tablespace or partition is self-describing.
  • SETCURRENTVERSION
    Modifies all tables at version zero to the current version of the tablespace. Use SETCURRENTVERSION with INSERTVERSIONPAGES.
A new REPAIRTS command is also now provided for the REPAIR utility. You can issue this command on storage groups, databases, tablespaces, and tables to generate the REPAIR utility on associated tablespaces.
The REPAIR command helps you to repair multiple tablespaces under the database or storage group by issuing the command only once.
When you issue the REPAIR command, the following processing occurs:
  • For database (DB) objects, JCL is generated for the REPAIR utility with appropriate REPAIR clauses.
  • For tablespace (TS) and table (T) objects, JCL is generated for the REPAIR utility with new REPAIR clauses.
When REPAIRTS is issued, the following processing occurs:
  • For storage group (SG) and database (DB) objects, JCL is generated for the REPAIR utility for all underlying tablespaces.
  • For tablespace (TS) objects, JCL is generated for the REPAIR utility for the tablespace.
  • For table (T) objects, JCL is generated for the REPAIR utility for the associated tablespace.
Implicit Object DDL Now Generated as Comments
The HDDL and DDL commands now generate DDL for implicitly created objects (database, tablespaces, tables, and indexes) as comments. The output DDL is appended with two dashes (--) as shown in the following example:
-- -- CREATE DATABASE DSN00009 -- BUFFERPOOL BP1 -- INDEXBP BP2 -- STOGROUP SYSDEFLT -- CCSID EBCDIC;
This formatting enables you to execute the generated DDL without having to comment out the implicit object DDL manually.
New OFS 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 customers when they 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.
New CREATE VIEW Default Option in OFS Parmlib Member
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 to inform customers when they are running with a setting that may not generate a CREATE VIEW column list that is consistent with the original CREATE VIEW statement.
Db2 12 Support
IBM Db2 12 for z/OS function levels V12R1M100, V12R1M500, and V12R1Mnnn are now supported. For a complete list of supported function levels, see the Db2 Version Support topic in the CA Database Management Solutions for Db2 for z/OS documentation on the Broadcom Tech Docs Portal.