This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. 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 (https://ideas.ibm.com).
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 updateson them if they matter to you. If you can't find what you are looking for,
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
Specific links you will want to bookmark for future use
prevent display DB2 version info displayed in header
Our CIP team uses a CIP Web application penetration scan to detect the header display that leads to the display of Db2 Version information. We need the ability to surpress this from being displayed as it violates company security best practice
Return information about a failed Lock-Escalation to the application
When a Lock-Escalation occurs it is documented by message DSNI031I (Lock Escalation has occurred) in the Db2-Master-Adressspace. But when a Lock-Escalation fails there is no documentation for this, instead it comes to a Timeout or Deadlock from a ...
Stored-Proc ADMIN_UTL_SCHEDULE: Add a Stop-Condition to continue when RC > 12 occurs
When a Db2-Utility started by Stored-Procl ADMIN_UTL_SCHEDULE abends the Reason-Code is passed back as the Return-Code. This happens for example if REORG fails due to problems with allocating SORTWORK-Datasets, especially for big tables, or when i...
Please do not make stabilizing dynamic query again after a REBIND with APPLCOMPAT a normal behaviour
Hello, We're DB2z 12 FL508. This is a SAP/R3 application on 2-way data sharing. We stablized access path of some dynamic SQLs and they worked very well. Note that the packages were at APPLCOMPAT V12R1M500 when we did this. Lately, the packages wer...
Hello! We had problems with CPU in Production environment several months ago with a simple query with IN predicate. The CPU reached 100%! Particularly, this query has many literals within IN predicate and the IN predicate can't be matching. After ...
Enhance DSNT375I deadlock message to include DRP global variable use
Following the introduction of the CURRENT LOCK TIMEOUT (CLT) special register and DEADLOCK_RESOLUTION_PRIORITY (DRP) global variable with EPIC 8876, the DSNT376I timeout message has been enhanced to show the timeout values used for both requester ...
Enhance high availability for partition by growth tablespaces.
Real-life scenario is described in the first paragraph below. I included a subset of it. The issue resulted in critical system outage caused a partition by growth dataset that hit max extents prior to hitting the DSMAX for the partition tablespace...
The DSNHBNFE member delivers a formal definition of the Db2 syntax in BNF format. However, tools like ANTLR can generate lexers/parsers automatically if the language is delivered in a EBNF format. https://en.wikipedia.org/wiki/Extended_Backus%E2%8...
KEY LABEL will likely be implemented at the application area, which means that there could be hundreds/thousands of objects impacted. The current solution presented is:
User objects - Set a key label using SQL interfaces (V12R1M502)
• ALTER / CRE...
z/OSMF workflow artifacts for Db2 UPDATE and ACTIVATE process
IBM z/OSMF workflows are being improved to be used for Db2 installation and migration. It would be nice if we have also the artifacts for the other CLIST processes: UPDATE and ACTIVATE. The UPDATE process is what we use the most.
Do not place IBM confidential, company confidential, or personal information into any field.