Skip to Main Content
IBM Power Ideas Portal

This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. 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 (

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
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Future consideration
Workspace IBM i
Categories Db2 for i
Created by Guest
Created on May 15, 2020

Temporal Support For System Tables

V7R3 of Db2 i introduced support for temporal tables. However, it is not possible for an end user to alter the system tables; such as QADBXREF / QADBIFLD, to be defined as temporal. Attempting to alter the table results in the following error message:

Message: [SQL0607] Operation not allowed on system table QADBXREF in QSYS. Cause . . . . . : The table or view QADBXREF in QSYS is a catalog or system table. Catalogs, system tables and system triggers cannot be changed or locked by the user.

Use Case:

Our software currently relies on the user "registering" tables to enable us to "capture" the record layout so we can process transactions from journal entries and map the journal entry data to the record layout. If we encounter a journal entry that indicates a change to the record layout we stop processing so that the user has to "re-register" the table with the updated record layout. This causes delay in processing that users wish to avoid.

Idea priority Urgent
  • Guest
    Feb 26, 2021

    IBM will use this request as input to planning but no commitment is made or implied. This request will be updated in the future if IBM implements it.

  • Guest
    Aug 13, 2020

    IBM has received the requirement and is evaluating it.

    IBM believes the requirement is to provide awareness when a table format changes. Temporal tables for catalog tables is a solution which will not be implemented.
    A more likely enhancement might be to define a new exit point for ALTER TABLE, which would allow you to take action when a table definition is modified.

    IBM will provide a response after evaluation is complete

  • Guest
    May 18, 2020

    I've added my vote. We're not interested in temporal tables, particularly, but the underlying requirement of being able to understand changes to the record layout is relevant to us.

    I'm going to piggyback on this to say that I would like to see IBM document the format used for D/CG journal entries. Currently the documentation just labels this as "internal data". We would ideally use the data in this journal entry to update our model of the data layout consumed from R/* journal entries. The best solution we can currently manage is to use the D/CG events to grab the current record format (which may not match, of course).