Data Replication

Expand all | Collapse all

IIDR with DB2 M505 on Z UTS support

Jump to Best Answer
  • 1.  IIDR with DB2 M505 on Z UTS support

    Posted Wed July 08, 2020 02:47 PM
    Since DB2 level M505 on z/OS does not support creation of non-UTS tablespaces, has IIDR install DDL been updated of UTS?
    Is there a conversion process provided to convert to UTS? One of the current tablespaces contain 25 tables.



    ------------------------------
    John Totzke
    ------------------------------


  • 2.  RE: IIDR with DB2 M505 on Z UTS support

    Posted Fri July 10, 2020 11:40 AM

    Hello

    IBM has an APAR open to modify the CHCMDMUT (CDC for zOS meta-data utility) to allocate UTS table spaces for the meta-data tables.

    Workaround : code the APPLCOMPAT keyword on the BIND statements in the CHCMDMBD sample JCL that binds the plans for the CHCMDMUT program


    ------------------------------
    Glenn Steffler
    ------------------------------



  • 3.  RE: IIDR with DB2 M505 on Z UTS support

    Posted Fri July 10, 2020 01:29 PM
    APAR will be released as PH22147. No release date scheduled at this time.

    ------------------------------
    Glenn Steffler
    ------------------------------



  • 4.  RE: IIDR with DB2 M505 on Z UTS support
    Best Answer

    Posted Tue January 05, 2021 04:04 PM
    Update: The fix for APAR PH22147 is now available.

    ------------------------------
    SARAH ORVIS
    ------------------------------



  • 5.  RE: IIDR with DB2 M505 on Z UTS support

    Posted Wed January 06, 2021 07:06 AM
    Thanks for the update on APAR PH22147 .
    But this is just a work around and does not bring IIDR up to DB2 M504 and above.
    IBM sets standards for the number of tables in a tablespaces, but then does not ensure their own products follow those standards.

    ------------------------------
    John Totzke
    ------------------------------



  • 6.  RE: IIDR with DB2 M505 on Z UTS support

    Posted Wed January 06, 2021 11:42 AM
    First, to be precise, it is DB2 V12R1M504 (Function Level 504), not DB2 V12R1M505 (Function Level 505) that imposes the deprecation of non-Universal Table Spaces. This is a deprecation, not a removal of support, so currently existing non-UTSes can still be used by applications for the foreseeable future.

    With regard to the responsibility for maintaining the IIDR CDC for z/OS table spaces, I refer customers to this section of the Knowledge Center documentation for IIDR CDC for z/OS:

    https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforzos.doc/concepts/preparingdb2udbforos390andzosv7db2forzosv8.html

    It points out that the IIDR CDC for z/OS meta-data table spaces contain application data, from DB2's standpoint, and the customer should treat them as such. The customer is responsible for the table spaces' continued health for the duration of their existence and use. In addition to taking regular backups and maintaining data restore procedures, these customer responsibilities include performing regular RUNSTATS to obtain the data needed to tune the performance of accessing the meta-data by IIDR CDC for z/OS and reBINDing the IIDR CDC for z/OS plans to incorporate that gathered data. These are the same as for any application data. Although not stated in the Knowledge Center, for a one-time action such as converting the table space format, this is also the customer's responsibility, as it would be for any application data.

    Until recently, if a customer was using DB2 V12 at FL 504 or higher and was attempting to create a new instance of IIDR CDC for z/OS meta-data tables, then the CHCMDMUT utility used to perform this action would fail to create new meta-data tables in new table spaces. This was due to CHCMDMUT attempting to create all but one of the tables in a single table space, which FL 504 (and higher) forces to be a UTS, and UTSes can only contain one table. This issue has been addressed by PTF UI71339. With this PTF applied, a separate UTS will be CREATEd for each meta-data table, and then the meta-data table will be CREATEd within it.

    PTF UI71339 does not provide any support for migrating currently existing meta-data tables from non-UTSes to UTSes. Nor should it or any PTF for IIDR CDC for z/OS do so, since FL 504 has deprecated non-UTSes, not dropped support for them. Meta-data tables contained in the non-UTSes are still fully usable and supported by DB2 at FL 504 and higher. PTF UI71339 addresses the one coercion that FL 504 does take, non-UTSes can no longer be CREATEd. If a customer desires or needs to convert the meta-data table spaces to UTSes then the customer must perform this action themselves, as they must do for any of their other application data table spaces.

    That being said, DB2 itself recognizes the effort required to perform such a table space format conversion for a large number of tables, and it has provided relief in FL 508 (APAR PH29392 in October 2020).  FL 508 adds a new MOVE TABLE clause to the SQL ALTER TABLESPACE statement.  MOVE TABLE provides assistance with the table space conversion. If a customer wants to convert the IIDR CDC for z/OS table spaces to UTSes, then they should explore the use of this new extension to the SQL ALTER TABLESPACE statement.

    ------------------------------
    Mark Hodsman
    ------------------------------



  • 7.  RE: IIDR with DB2 M505 on Z UTS support

    Posted Mon November 09, 2020 12:51 PM
    Thank you for posting your message. I hope I can find some interesting stuff here.

    ------------------------------
    Linda Taylor
    ------------------------------



  • 8.  RE: IIDR with DB2 M505 on Z UTS support

    Posted Mon February 22, 2021 11:11 AM
    This is very helpful, thanks everyone!

    ------------------------------
    Jesse West
    ------------------------------