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.
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-24.00.00.000000'. However, using this value can lead to various problems which are recognized by DB2 development already as during introduction of temporal tables, the maximum timestamp for temporal objects generated by Db2 is '9999-12-30-00.00.00.000000'
Below quote from PMR with IBM explanation why currently documented maximum timestamp is wrong and in fact should not be used.
when you use a getTimestamp or getString call to retrieve data from a TIMESTAMP(p) column, the IBM Data Server Driver for JDBC and SQLJ converts the value to a java.sql.Timestamp. It turns out that java.sql.Timestamp is based on java.util.Date which represents hours as values from 0 to 23. Unlike the DB2 family support of SQL, the value 24 is not part of the lexical representation for Java. Hence, 24.00.00.000000000000 becomes 0.00.00.000000000000 of the next day. For example, the value '2010-11-03-24.00.00.000000000000' would be shown as '2010-11-04-00.00.00.000000000000'. Apart from Java tools such as Data Studio, this issue may lead to problems (or confusion) for Java developers. With the DB2 10 for z/OS support of bitemporal data, this problem is further amplified because a maximum timestamp value is stored in the ROW END of every column in a system-period temporal table. DB2 uses '9999-12-31-24.00.00.000000000000' as that end value, and when these timestamp values are later externalized through Data Studio they are returned as as 10000-01-01 00:00:00.0 which does not make sense to the user because DB2 does not support 5-digit years.
SQL council agreed that better value will be in the temporal tables case the '9999-12-30-00.00.00.000000' - also to allow conversion from data type timestamp without timezone, to timestamp with timezone, which would end in error for value like currently documented maximum timestamp.
This should be changed and maximum value should be unified across all objects with some possible migration help otherwise it seems like DB2 development consciously allows to use value which is not fully supported by DB2 and which in result present a problem.
Do not place IBM confidential, company confidential, or personal information into any field.