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 Not under consideration
Workspace Db2 for z/OS
Created by Guest
Created on Aug 14, 2017

Joining a temporal table with an archive-enabled table

In DB2 z/OS V11.1, we getting a -20555 SQLCODE when trying to join a temporal table with an archive-enabled table. We were surprised to see it didn't work. The manual talks about those tables being “mutually exclusive”, which to me would mean you can't define a table as both.
At present you can join two temporal tables together and you can join two archive-enabled tables together, but you can't join a temporal table to an archive-enabled table.
We would like the ability to join a temporal table to an archive-enabled table. Even if it were limited to a join with no “time-travel” option and not setting the GET_ARCHIVE variable, it would be a big help to at least be able to join the two "base" tables together.
  • Admin
    Janet Figone
    Reply
    |
    Dec 5, 2022

    Dear Ron,

    Thank you for submitting this Db2 for z/OS Idea. After giving the request a comprehensive review, we have determined that we cannot include it as a candidate in an upcoming deliverable because it is not consistent with our product strategy for future deliverables. Consequently, we will have placed it Not under consideration at this time.

    We appreciate your input to the Db2 for z/OS development team. We also hope that you will continue to submit enhancement suggestions for improvements as customer feedback is a key component to shaping the future direction of Db2 for z/OS.

    Sincerely,

    Db2 for z/OS Team

  • Guest
    Reply
    |
    May 8, 2019

    From the Word document of all the cases, the two we are most interested in are 6c and 9d.  Those have an X in the attached document.

    We only have one set of Application-period temporal tables (ATT) so those are not a great concern.  We have quite a few System-period tables (STT).  We would like to do more archive-enabled (AET) but this restriction has kept us from doing many.

    Therefore, the most basic case in both static and dynamic applications is to allow the joining of the "base" STT and AET tables.  We don't use FOR SYSTEM_TIME AS OF construct on the STT queries very often, so that in combination with an AET should be rare.  

    Being able to set GET_ARCHIVE in a join with a base STT table would probably be the next most desired option.  I guess that would be options 6a and 9b.  

    Both of the questions in the Word doc about something being acceptable (points 7 and 8) are fine. 

  • Guest
    Reply
    |
    May 7, 2019

    Janet,

    Let me start with answering questions b, c, and d.  

    b. I am just running a dynamic sql query in a query tool.

    c. The package used for the dynamic statement is SYSSN200.  It is bound with all those options set to 'Y'

    d.  I didn't set any of these special register options or the global variable.  I simply ran a query that joined a system temporal table with archive-enabled table.  

  • Admin
    Janet Figone
    Reply
    |
    Apr 16, 2019

    Our engineer has provided a word doc, attached, and also has the following questions for you regarding this idea.

    a. the customers want that temporal tables (STT, ATT, BTT) and archive-enabled table (AET) can be contained in the same SQL statement (or we call "query"), they dislike the restriction with SQL error code
    b. for above query that expected to be successful, it is dynamic query or static query in their applications?
    c. when they run above query, what are the values of the bind options SYSTIMESENSITIVE, ARCHIVESENSITIVE, BUSTIMESENSITIVE?
    d. when they run above query, what are the values of special registers CURRENT TEMPORAL SYSTEM_TIME, CURRENT TEMPORAL BUSINESS_TIME, and global variable GET_ARCHIVE?