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 Jun 30, 2023

In SQL JSON_TABLE, add an option on timestamp columns to take into account or not the timezone offset

In the SQL function JSON_TABLE, when a timestamp value indicated with a time zone offset (e.g.: "yyyy-mm-ddThh:mm:ss.nnnnnn<+/-Offset>") is retrieved to produce a timestamp column, the resulting value is always an UTC value (by adding or subtracting the indicated time zone offset), not a local value (without taking the offset into account).

However, it's often the case that you don't want to transform the local value of a timestamp into a UTC value. For example, web services implemented in LWI automatically convert the value of a timestamp parameter into a value with the time zone offset. So if you expose a web service in LWI and consume it in a SQLRPGLE, the value retrieved will be different from the one in the database if you're not in the UTC time zone.

As with other databases, it would be interesting to have an option on the timestamp column to indicate whether the time zone offset should be taken into account or not:

select * from json_table('{"root" : {"ts1" : "2023-05-31T12:21:57.123456+02:00"}}', 'lax $.root[*]' columns(ts1 timestamp TIMEZONE|NOTIMEZONE PATH 'lax $.ts1'));

Another solution would be to have another type of timestamp column to indicate whether the resulting timestamp should be produced taking into account the time zone offset or not:

select * from json_table('{"root" : {"ts1" : "2023-05-31T12:21:57.123456+02:00"}}', 'lax $.root[*]' columns(ts1 timestamp|timestamp_notimezone PATH 'lax $.ts1'));

Idea priority Medium
  • Guest
    Oct 18, 2023

    The CEAC has reviewed this requirement and recommends that IBM view this as a MEDIUM priority requirement that is important to address.

    Background: The COMMON Europe Advisory Council (CEAC) members have a broad range of experience in working with small and medium-sized IBM i customers. CEAC has a crucial role in working with IBM i development to help assess the value and impact of individual RFEs on the broader IBM i community and has therefore reviewed your RFE.

    To find out how CEAC help to shape the future of IBM i, see CEAC @ and the article "The Five Hottest IBM i RFEs Of The Quarter" at

    Sabine Jordan + Sara Andres – CEAC Program Manager, IBM

  • Guest
    Jul 24, 2023
    IBM will use this Idea as input to planning, but no commitment is made or implied. This Idea will be updated in the future if IBM implements it.

    Is your request to ignore the timezone offset completely? Or something else. There are several interpretations of what this timezone portion might mean.

    Db2 for i development
    IBM Power Systems Development
    1 reply