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,
Post an idea
Upvote ideas that matter most to you
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.
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.
In reference to this Db2 for z/OS idea (link), we need the same functionality for all platforms including Db2 for LUW.
I quote the text from the other RFE:
Currently there is documented maximum timestamp value available in DB2 as '9999-12-31-2...
Allow data type ROW CHANGE TIMESTAMP in column-organized tables
We need the ability to define columns with data type ROW CHANGE TIMESTAMP in our tables so that we can track when the last change was made. Currently we use normal row based tables which allow this but we want to migrate to column based tables. Wh...
Do not place IBM confidential, company confidential, or personal information into any field.