Installation and Configuration Enhancements
The following installation and configuration enhancements have been made in this release:
The following installation and configuration enhancements have been made in this release:
For upgrade instructions, see Upgrade to a New Product Release.
Post-Install Enhancement to Support Non-Db2 for z/OS Binds
CA Database Management Solutions for DB2 for z/OSpost-install tailoring process has been enhanced to let you specify remote DRDA locations for remote binds.
The following changes have been made:
- A new column, Location Type, has been added to the Edit Parmlib Member SETUP panel (INSEDSE5) so that you can specify whether the Db2 subsystem is running on z/OS or a remote DBMS system that supports DRDA access.
- The bind skeletons have been updated to conditionally include new bind statements for DRDA locations.
To align our installation of the
CA Database Management Solutions for DB2 for z/OSwith SMP/E best practices, the following changes have been made:
- In the DSNAME global parmlib member, SRCLIB now points to the CDBASAMP target data set instead of CDBASRC.If you are upgrading from an earlier release, we recommend that youdo notcopy the DSNAME global parmlib members from an earlier release. These DSNAME members will not work for new releases due to the creation of new target libraries and elements being moved between libraries. Instead, you should use the Edit Global Parmlib Members option to create new DSNAME members. The automatic pre-population of libraries will ensure that the appropriate target libraries are associated with each parameter.
- The following data sets are new:
These new data sets contain members that previously existed in CDBASRC and CDBASAMP. In addition, some members from CDBASRC have been moved to CDBASAMP.
- CDBAGTF (Variable length data)
- CDBAJCL (Sample JCL)
- CDBAMAC (Assembler Macros)
- CDBAPROC (JCL Procedures)
- CDBASQL (SQL, DDL, and DML)
Pax-ESD Processing Improvements
The pax-ESD installation process has changed to be more efficient for installers. When you download a new pax file for this release, note the following changes:
- HOLDDATA is now acquired and processed after the base product installation is accepted.
- Only zFS file systems are now supported in the installation jobs. HFS is no longer supported.zFS is the strategic file system for z/OS UNIX. IBM recommends that you migrate from HFS file systems to zFS file systems before installing z/OS V2R1.
- Jobs are now run in the following order (new and old job names are shown in parentheses):
- Allocate product and SMP/E data sets (DBM00ALL replaces DBM2ALL)
- Allocate product USS data sets (DBM03ALU replaces DBM2ALLU)
- Allocate product USS directories (DBM06MKD replaces DBM3MKD)
- Create and customize SMP/E CSI (DBM10CSI replaces DBM3CSI)
- Customize SMP/E CSI for USS (DBM15CSU replaces DBM3CSIU)
- SMP/E RECEIVE of base function (DBM20RCB replaces DBM4RECD)
- SMP/E APPLY of base function (DBM30APB replaces DBM5APP)
- SMP/E ACCEPT of base function (DBM40ACB replaces DBM6ACC)
- Download CA Recommended Service ASSIGN statements (DBM50CAR replaces DBM7CARS)
- SMP/E RECEIVE of HOLDDATA (DBM60RCH replaces DBM7RECH, DBM1HOLD is no longer used)
- SMP/E RECEIVE of downloaded PTFs (DBM70RCM replaces DBM7RECP)
- SMP/E APPLY of downloaded PTFs (DBM80APM replaces DBM8APYP)
- SMP/E ACCEPT of downloaded PTFs (DBM90ACM replaces DBM9ACCP)
During the UNZIP process, only the SAMPJCL is copied to DASD. The RECEIVE process has been changed to RECEIVE FROMNTS. The RECEIVE FROM NTS processes the RELFILES directly from the SMPNTS directory. Before this change, the RELFILES were received from DASD.
For more information about these installation procedures, see Install Products Using Native SMP/E JCL.
Db2 12 Continuous Delivery Model Support
Version 20.0 of the
CA Database Management Solutions for DB2 for z/OSsupports the Db2 12 Continuous Delivery Model. To enable the
CA Database Management Solutions for DB2 for z/OSto be able to specify the Db2 12 function levels and catalog levels, the following new parameters have been added to the SETUP global parmlib member:
- Function Level (SSIDVERF)
- Catalog Level (SSIDVERC)
During post-install tailoring, these new parameters are now displayed on the Edit Parmlib Member SETUP panel (shown in bold text on the following sample panel) and in the SETUP parmlib member (
hlq.CDBAPARM) after editing. Both values are required.
-------------------------- Edit Parmlib Member SETUP ------------------------- OPTION ===> PF KEYS......: ENTER to Continue, PF1 for Help Member..: SETUPxx PF3/END to Return to the previous panel COMMANDS.....: CANCEL to Exit without Saving Changes DB2 Subsystem.................> ssid DB2 Subsystem Description.....> DB2 11 going to DB2 12DB2 12:Function Level...> D12R1M500Catalog Level........> V12R1M500 DB2 10/11: Version..........> Mode.................> VSAM Catalog Alias............> ssid DB2 Load Libraries............> ssid.PRIVATE.SDSNEXIT ...........> hlq.SDSNLOAD ...........> ...........> BSDS01 Dataset................> ssid.BSDS01 BSDS02 Dataset................> ssid.BSDS02 DB2 ZPARM Library.............> hlq.SDSNEXIT DB2 ZPARM Member..............> ssidPARM Install SYSADM................> USERA01 Install SYSADM2...............> USERA01
When configuring a Db2 12 Continuous Delivery subsystem, do not specify values in the Db2 10/11 Version and Mode fields. These values are mutually exclusive with the Db2 12 Function Level and Catalog Level fields.
When upgrading from Release 19.0 and editing a Db2 12 subsystem, the parmlib editor automatically converts the previously specified Version and Mode values are automatically converted to Db2 12 Function Level and Catalog Level values. A message displays informing you about the conversion. You can no longer specify Db2 12 values in the Version and Mode parameters.
New Xmanager Execution Parameters
Support for two new optional parameters has been added to the execution manager (Xmanager) address space. These parameters can help Xmanager effectively manage excessive storage conditions.
You can now add the following parameters to the Xmanager started task procedure in
- MAXAUX(int)Specifies the maximum number of auxiliary storage slots, in K, that can be used to back the above-the-bar storage. For example, MAXAUX(500) specifies 512,000 slots.Limits:100 to 99999
- MEMMAX(int)Specifies the maximum amount of virtual storage, in GB, that can be allocated above the 2-GB bar. For example, MEMMAX(12) specifies 12 GB. This parameter is the equivalent of the MEMLIMIT parameter on the JOB or EXECUTE card. Use MEMMAX only when the IEFUSI exit contains a MEMLIMIT value that is overriding the MEMLIMIT value in the JCL and causing excessive storage usage above the bar.If your MEMMAX value exceeds the MEMLIMIT value in the JCL, the MEMMAX value is reduced to match MEMLIMIT.Limits:1 to 99999
Update of LOCKSIZE attribute to ROW for PTG700T2 tablespace
The LOCKSIZE attribute of the PTG700T2 tablespace has been updated to ROW to reduce the risk of contention on the restart table. Previously, the LOCKSIZE attribute was set to PAGE. The PTG700T2 (tablespace) identifies the secondary restart tablespace for the utilities. The ROW attribute for LOCKSIZE is recommended to avoid contentions on the restart table. You no longer need to use the ALTER command to update the LOCKSIZE attribute to ROW on the PTG700T2 tablespace.
New UTIL Parmlib Options to Establish Default RECLUSTER Settings in CA Fast Load
CA Fast Load for DB2 for z/OS(CA Fast Load) now gives you the ability to establish the default RECLUSTER keyword settings for all jobs. This keyword specifies whether to sort the data and the clustering index during the load. Previously, specifying RECLUSTER in your SYSIN syntax was the only way to control these sorts.
This functionality is provided by the following new options in
- PFL-RECLUSTER-DEFAULTSpecifies what to sort when you omit RECLUSTER from SYSIN. You can sort the clustering index only(SORT-CLINDX), sort the clustering index and data (SORT-ALL), or no sort (SORT-NONE).
- PFL-RECLUSTER-NOSpecifies whether to sort the clustering index during a load. You can specify no sort (SORT-NONE) or sort the clustering index only (SORT-CLINDX).
- PFL-RECLUSTER YESSpecifies what to sort during a load. You can sort the cluster index and data (SORT-ALL), sort the clustering index only (SORT-CLINDX), or no sort (SORT-NONE).
The existing RECLUSTER NO and YES keyword options in SYSIN now use the new UTIL parmlib settings:
- NO uses the PFL-RECLUSTER-NO value.
- YES uses the PFL-RECLUSTER-YES value.
The default parmlib settings provide the same product behavior that RECLUSTER NO and YES previously provided. However, if you change the parmlib settings, RECLUSTER NO and YES will behave differently. For more information, see the RECLUSTER keyword description.
You can override the parmlib settings by using the following keyword options:
- The existing NO SORT-CLINDX keyword option
- The followingnewkeyword options:
- NO SORT-NONE
- YES SORT-CLINDX
- YES SORT-ALL
CA Fast Load documentation
New AUTO option for the LARGE-TAPE-BLOCK Parameter in the UTIL Parmlib Member
The LARGE-TAPE-BLOCK keyword and UTIL parmlib option have been enhanced with the new option AUTO. The AUTO option detects and uses the maximum block size available to a device. The YES option now functions the same as the AUTO option.
CA Quick Copy documentation
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. When the original CREATE VIEW statement does not have a column list, a column list is not generated. 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.
CA RC/Migrator and CA RC/Compare documentation
CA RC/Extract documentation
CA RC/Query documentation
CA RC/Update documentation
DB2 Catalog Customization and Model Services Changes in CA RC/Migrator
The following install and configuration related changes have been made in
CA RC/Migrator™ for DB2 for z/OS(CA RC/Migrator):
The instructions in the RCMCUST customization information member have been enhanced to describe how to activate the new IDENTITY and SEQUENCE utilities in the @DEFAULT model. IDENTITY executes the RMRTPE REXX stored procedure that resets identity column numbering after a table reload. SEQUENCE executes the RMRSQPE REXX stored procedure that prevents duplicates for altered sequences.
The RCMCUST member was also updated to remove the optional task for implementing parallel unload and load processing. This processing is now delivered with the product.
New %DTQUAL automatic symbolic
The new %DTQUAL automatic symbolic is used in the following utility models when it is included in your DSN override:
- CHECK, CHECK_R
- COPY, COPY_B, COPY_PC, COPY_R, QCOPY, QCOPY_B, QCOPY_R
- FUNLD, FUNLD_B, FUNLD_R, IBMULD, IBMULD_B, IBMULD_R, UNLOAD, UNLOAD_B, UNLOAD_R, XUNLD
- OREORGT, OREORGTS, REORG, REORG_R, REORG_I, REORGI, REORGI_R, RREORG, RREORG_R, RREORGI, RREORI_R
Use of %DTQUAL ensures that a unique data set name is created when allocated.
The DSN override is set in the Batch Processor DSN mask field when you load and customize the model services table during DB2 catalog post-install customization. We recommend setting this field to %USERID..%DSNQUAL2..%DSNQUAL3..%DTQUAL.
Template statements are now supported as the default data set allocation method (USETMPLT is YES) in the following utility models: CHECK, CHECK_R, COPY, COPY_B, COPY_PC, COPY_R, IBMULD, IBMULD_B, REORG, REORG_R, REORGI, and REORGI_R.
You can now use TEMPLATE syntax or .ALLOC syntax to allocate data sets. To use .ALLOC, you must update the model to activate.
Additionally, the following utility models have been updated to use %LARGE to determine the UNIT value for the TEMPLATE statement: COPY, COPY_B, COPY_PC, COPY_R, IBMULD, IBMULD_B, IBMULD_R, OREORGT, OREORGTS, REORG, REORG_R, REORGI, and REORGI_R. This support ensures that virtual tape use is successful for LARGE data set processing.
With the exception of image copy data sets (PTICOPY TEMPLATE), only the &PART and &PA Db2 symbolics are supported in TEMPLATE data sets and only one instance of these symbolics is allowed in the data set name. For image copy data sets specified with PTICOPY TEMPLATE, the use of IBM Db2 symbolics is unrestricted.
The REORG, REORG_R, RREORG, and RREORG_R utility models have been updated to ensure that LOB objects are supported.
SHRLEVEL CHANGE Support
The REORG and REORG_R utility models have been converted from SHRLEVEL NONE to SHRLEVEL CHANGE.
The RREORG and RREORG_R utility models have been converted from SHRLEVEL NONE to DATA-AVAILABLE CRITICAL, which is equivalent to SHRLEVEL CHANGE.
Parallel IBM UNLOAD/LOAD Support during Recovery
The IBM UNLOAD recovery utility model (IBMULD_R) now generates a recover data set with &PART in it when &PART is added to &DATADSN. The LOAD_R utility model generates load data sets with &PART in the analysis file.
The following changes have been made to the LOAD_R model:
- Template statements changed to use new auto-symbol %TMPLTDSN
- INTO clause built using #SEG/#ENDSEG logic
By default, parallel processing is off. To activate, edit IBMULD_R and change symbol DATADSN to %DSN..P&PA..RD.
Isolation Level Support in CA RC/Query and CA RC/Update
A new RCQ parmlib member for
CA RC/Query® for DB2 for z/OS(CA RC/Query) is now provided in the
hlq.CDBAPARM data set and the post-install tailoring panels for the product-specific parmlib members. This new member includes a new isolation level parameter (GLOBAL_ISOLATION_LEVEL), which enables you to specify the isolation level at the global level for queries in CA RC/Query.
You can also edit the RCQ parmlib member using the EP option from the products Main Menu.
CA RC/Update™ for DB2 for z/OS(CA RC/Update), a new global level parameter, ISOLATN, has been added to the RCEDIT parmlib member in the
hlq.CDBAPARM data set. CS is the default. For user level support, a new parameter RC Browse Isolation Level is now provided on the RC/Edit Parameters panel. If left blank (the default), the global level setting is used.
APPLCOMPAT Bind Support
The APPLCOMPAT bind option is now used to bind packages when you execute the Bind Product Plans and Packages task during post-install tailoring of the
CA Database Management Solutions for DB2 for z/OS. You must regenerate and rebind the CA Database Management Solutions for DB2 for z/OS when you upgrade to a new function level.
Changes to FMID CINSK00
The following new components have been added to the CA DBM common services (base) FMID (CINSK00):
- Database Management Data Service (DBM Data Service)The DBM Data Service hosts a RESTful API that enables access to Db2 data and metrics that are collected byCA Detector® for DB2 for z/OS(CA Detector) andCA SYSVIEW® Performance Management Option for DB2(CA SYSVIEW for DB2).More information:
- Mainframe Team Center user interfaceMainframe Team Center is a graphical user interface that lets you view and analyze Db2 application performance data from CA Detector from a web browser
In addition, all SQL parser content has been moved to FMID CSQ2100 CA Common SQL Services for DB2 for z/OS. SQ2 Common SQL services is now included with the following products and components:
- CA Database Analyzer™ for DB2 for z/OS
- CA Detector® for DB2 for z/OS
- CA Fast Unload® for DB2 for z/OS
- CA Log Analyzer™ for DB2 for z/OS
- CA Plan Analyzer® for DB2 for z/OS
- Post-install tailoring of theCA Database Management Solutions for DB2 for z/OS
- CA RC/Migrator™ for DB2 for z/OS
- CA RC/Query® for DB2 for z/OS
- CA RC/Update™ for DB2 for z/OS
- CA SQL-Ease® for DB2 for z/OS
- Utilities common (CPUTK00)
- Utilities general recovery (CUGRK00)
New Auto Delete Option in PDT Parmlib Parameter
If a data set in a data store becomes full, CA Detector can now delete multiple collection intervals from the data set to make space for the newest interval. Previously, CA Detector stopped writing data to the data store. This new functionality lets CA Detector continue to write collection data to the data store even when the data store has become full.
This new functionality is enabled by adding the INTERVAL_%_TO_DELETE (
nnn) parameter to the PDT parmlib member in
high-level.CDBAPARM. This parameter specifies the maximum percentage of collection intervals to delete. For example, if you specify 50 percent and the data store contains 60 intervals, CA Detector can delete up to 30 of the oldest intervals to make space for the newest interval. Valid values are 0 to 100. The default is 0.
See Set the Auto Delete Threshold for Collection Intervals in the CA Detector documentation.
New Option for the PRE_ALLOCATE Parameter in the PLA Parmlib
The PRE_ALLOCATE parameter now has a new option, (E,x). This option enables the use of parallel tasks to reduce the elapsed processing time of your jobs when recalling archive log data sets. The description for the parameter is updated in the PLA parmlib panel.
Enhanced Behavior of the SHRLEVEL (S)kip Option in the PLA Parmlib
SHRLEVEL (S)kip in the PLA parmlib member has been enhanced to process SHRLEVEL CHANGE image copies instead of skipping them when the PIT_RBA for the image copy in SYSIBM.SYSCOPY is lower than the log point of the first incomplete update within the same tablespace that the image copy was taken for. The description for the parameter is updated in the PLA parmlib panel.
New UTIL Parmlib Option to Determine whether
CA Quick Copy for DB2 for z/OSshould Process SHRLEVEL CHANGE Incremental Image Copies
The new parmlib option PQC-SHRLEVEL-CHANGE-POLICY (
NORMAL|STRICT) has been introduced to specify whether to continue processing SHRLEVEL CHANGE incremental image copies or to terminate with RC=8 under the following conditions:
- The START_RBA of the image copy is unknown.
- The START_RBA of the image copy is the same value as a previously created image copy and cannot be registered to SYSIBM.SYSCOPY.
The description for the parameter is available in the UTIL parmlib panel.
Snapshot General Services DFSMSDSS Performance Enhancements
Snapshot General services has improved performance and provided CPU time reduction when using z/OS DFSMSdss services as a copy method. Extended TIOTs (XTIOT) are used to allow more than 255 data sets to be processed in a single run.
To enable the DFSMSdss copy method, specify USEDFDSS(YES) in the TG10INIT subsystem initialization job.
In the future, Snapshot General Services will be enhanced to use the z/OS DFSMSdss services copy method by default. The current default is USEDFDSS(NO).
New RCX Parmlib Options for Data Masking with Test Data Manager
Intelligent data masking is now provided with the integration of
CA RC/Extract™ for DB2 for z/OS(CA RC/Extract) with Test Data Manager. The following new RCX parmlib parameters must be configured:
- TDM API Db2 plan name
- TDM API message KSDS file
- TDM API load library file
You can obtain these values from the Test Data Manager administrator. For more information about these options, see the RCX parmlib member using the EP (Edit Parmlib Member) option on the Main Menu.
Post-Install Tailoring Enhancements
The CA Database Management Solutions for DB2 for z/OS post-install tailoring process has been enhanced to facilitate easier and quicker navigation through the panels that are available from the CA Products for DB2 for z/OS Post-Install Tailoring menu to facilitate easier and quicker navigation through the panels.
This functionality includes:
- Updating the look and feel of the Post-Install Tailoring panels across all options to ensure consistency when making edits and executing changes.
- When setting up global parmlib members, the SETUP Subsystem Edit Selection panel (INSEDSE2) has been updated to include:
- The new FIND/LOCATE SSID command to quickly select a relevant subsystem ID when a large number of Db2 subsystems are displayed.
- The new SORT command that lets you sort the columns on the panel in ascending or descending order to quickly find and update subsystems that are marked in error.
- When executing Db2 catalog customization tasks
- Processing of the Select DB2 Subsystems panel (INSSLDB2) is now faster and you can use the new FIND/LOCATE SSID command to quickly select a relevant subsystem when a large number of Db2 subsystems is displayed.
- The Select DB2 Tasks panel (INSSLTSK) now displays the task ID for each task to help with orientation when generated task members have been renamed.
- Obsolete and irrelevant Db2 catalog customization tasks have been removed as follows:
- ACM Table Conversion Task
- ALOGRANGE Table Conversion Task