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.
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...
Profile Tables today support only remote connections and no support for local/batch applications. When PT is used to set certain registers, it only works for remote applications and local apps needs to be changed to add certain SET commands.
Rebinding/Binding old native stored procedure packages
Let’s say you have a native SQL stored procedure package. And it was created/bound on Db2 V10 system. And you’d like to bind/rebind that same native SQL stored procedure package to V12R1M50+ (Let’s say for version next, if there is such a thing). ...
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.
Client Application Name (QMDAAPPL from IFCID 0003) used in column RLFEUAN from SYSIBM.DSNRLMTxx tables to governor distributed applications
We would like to use table SYSIBM.DSNRLMTxx (SYSIBM.DSNRLMT01) in order to avoid that certain applications, coming from distributed environment and reaching Db2 for z/OS through DDF, can execute SQL statements. We’d like to completely block these ...
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 ...
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 ...
Since the requirement to have a Package for Dynamic SQL was introduced there has always been the problem about when to REBIND these "empty shells". The requirement to REBIND was only slightly annoying in the past as it was just to avoid an auto bi...
Do not place IBM confidential, company confidential, or personal information into any field.