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.
Difficulties to migrate from old tablespace types to UTS.DB2 V10 gives us the opportunity to use the ALTER-syntax to change tablespace type from SIMPLE or SEGMENTED to UTS PBG without (almost) any outage. Unfortunately there is a limitation which ...
DSNT376I message don't supply total information to solve the problem analisys
I found that as soon as the DB2 Lock Escalation message occurred (DSNI031I), DB2 seems to begin rejecting the ESS SQL calls against this tablespace, *immediately* without waiting the DB2 lock timeout interval. This probably explains why there is n...
Provide a ZPARM to prevent creating new non UTS-tablespaces
I have converted all single table tablespaces to UTS, but some days later new non UTS-tablespaces were created, which I again converted. And again new ones were created, so this process could go for ever.
Hello, Since we are in DB2 V10 we use triggers with bi-temporal tables (system temporal + business temporal table) to implement complex relational integrity rules that can not be defined using standard primary/foreign keys. It's related to simple ...
Read all SQL statements from dynamic statement cache
Storage areas in DB2 become bigger and bigger, so does the dynamic statement cache. When reading the DSC data with the IFI function READS (IFCID 316) the possibility to get an RC 00E60833 increases, when specifying a return area that is large enou...
Since V10 there is implicit casting, which is one hand a good feature, but on the other hand can lead to big performance problems. Improve the implicit casting so that the resulting datatype is indexable, e.g. make SELECT ... FROM T1 WHERE Integer...
Do not place IBM confidential, company confidential, or personal information into any field.