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

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:

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

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Additional Information

To view our roadmaps:

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is:

Status Not under consideration
Workspace Db2
Components Data Types
Created by Guest
Created on Mar 25, 2015


Competitive databases like Oracle, PostgreSQL and SQL Server along with others have data type TIMESTAMP with TIME ZONE but LUW does not.

Our own DB2 on z/OS starting version V11.0 has TIMESTAMP WITH TIMEZONE.
  • Guest
    Feb 18, 2022

    Why is this idea marked "Not under consideration"? We opened a support case about this RFE, and were told that the DB2 LUW engineers were well aware of the need for the timestamp with timezone data type, and it is current in your development plan, but that no ETA had been established yet. If that is the case, the status of this idea/RFE is misleading.

    IBM seems to be falling behind the others in the marketplace, because as the original author of this RFE stated, Microsoft SQL Server, Oracle, PostgreSQL and others have this data type already. IBM DB2 customers are also falling behind as a result.

    It would be excellent if an ETA were released, so that we could see light at the end of this tunnel.

  • Guest
    Jun 7, 2021

    With the assumption that it should be available in the DEFAULT clause and not just in isolation