Skip to Main Content
IBM Data and AI Ideas Portal for Customers


This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:


Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,


Post your ideas

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Employees should enter Ideas at https://ideas.ibm.com


Status Delivered
Created by Guest
Created on Nov 3, 2021

IIDR CDC : Remote Db2 z source, microseconds precision to DM_TIMESTAMP

IIDRCDC for Remote Db2 Source is relatively new IBM product that replicates data from Db2 z/os but some part of CDC engine can be remote from z/OS. In this particular scenario, source is Db2 z/OS using remote Db2 IIDR and target is flat file using IIDR CDC Datastage product.

IIDRCDC generates source commit timestamp from Db2 logs in the IIDR metadata variable "DM_TIMESTAMP" . IIDRCDC usually gets it from Db2 logs. Currently IIDRCDC for Remote Db2 z Source can get this timestamp only up to millisecond precisions instead of microsecond precision. Below is example of both values.

IIDRCDC remote Db2 z source : current Support.

milliseconds precision for DM_TIMESTAMP => 2020-08-31 10:10:42.466

Traditionally IIDRCDC for DB2 z Source (non-remote engine) provides six digit precision for this like below.

microsecond precision for DM_TIMESTAMP=> 2020-08-31 10:10:42.466137

This request is to provide same level of microsecond precision for Db2 remote z Sources.

Per IBM support, this is due to CDC for Db2 Remote z Engine is written in Java and there is a Java engine limitation for JCF &TIMSTAMP up-to millisecond only. This functionality is supported for CDC z source (non-remote), where Engine is written in C programming language.

This is very useful timestamp to identify CDC patterns and exact transactions order in the source database and very useful in fraud detections and analytics. If source database has more than one DML transactions within few microseconds apart, IIDRCDC output would not able to differentiate it. As Most of OLTP or batch workload in the source databases are usually fractions of microseconds, this is very crucial functionality for IIDRCDC to have.

Needed By Month
  • Guest
    Reply
    |
    Mar 30, 2022

    I was able to test out this fix that is available on latest IIDR fixpack, here is findings.

    1. For IIDR CDC Process (mirror or normal replication), IIDR metadata column timestamp reflects six digit precision.

      • Example: 2022-03-14 08:52:29.314783 (This is good)

    2. For IIDR Refresh process (Getting existing data from table), IIDR is only getting 3 digit precision for IIDR metadata column timestamp and padding three zero’s.

      • Example: 2022-03-14 10:46:24.697000 (IBM, Please review)

    In summary, issue is fixed partially. IBM - if you can review second part that would be great.