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.
select ... from final table ( update table for portion of business time from ... )
the problem is that an update table for portition of business time can effect more than 1 row and if this is made in a bitemporal environment the System Start is set to the first change timestamp. But you didn't know the exact time you have to rea...
Allow RUNSTATS SHRLEVEL CHANGE to operate as the name says
This RFE is a result of the PMRs (31614,112,848) we have opened where the root cause was identified as invalid values in RTS tables. Current design allows to re-initialize certain fields in RTS (eg. TOTALROWS) only by executing RUNSTATS SHRLEVEL R...
We use Db2 Connect as a gateway to access Db2 z/OS. We have several situations where a user connects to Db2 z/OS using an invalid password and the user is revoked. On the Db2 z/OS side, only the Db2 Connect IP (gateway) is registered. I would need...
over 1 year ago
in Db2 for z/OS
Planned for future release
Allow the setting of a global option make LOAD jobs fail if a PRESORT cannot be performed
UET will be withdrawn from support next year and its use needs to be removed. To do this the newly provided support for the PRESORT keyword in the LOAD utility needs to be the same and consistent as the functionality that UET provided for PRESORT....
Add support for PDS input files to PRESORT in LOAD
The Utilities Enhancement Tool (UET) provides support for the PRESORT keyword for LOAD. It will sort the input file and pass it to LOAD to perform the LOAD. It will accept the input file as being a PDS and perform a PRESORT. UET will be withdrawn ...
Include SYSPACKSTMT.STMT_ID in GET DIAGNOSTICS data
The SQL Standard for GET DIAGNOSTICS includes details about the actual statement being diagnosed - COMMAND_ FUNCTION / _CODE and DYNAMIC_FUNCTION / _CODE. The Db2 implementation includes none of these. Making it, effectively, impossible to identif...
Distributed Thread cancelled due to Idle Thread Timeout or MONITOR IDLE THREADS not writing record to SYS1.LOGREC
We noticed that every DB2 distributed thread that is cancelled because:
1) Idle thread timeout value that is specified by Db2 subsystem parameter IDTHTOIN in macro DSN6FAC is exceeded; or
2) ATTRIBUTE2 value in a row with KEYWORD value MO...
Full Column Match and I1 Access on SQL with Correlated Sub-Queries Containing Column Expressions and Supporting IoE
Some queries with column expressions - DATE(A1.EFCTV_TS) <= DATE('04/05/2020') for example, and an Index on Expression to support the expression are achieving I1 access while others are not. It appears this is because of how the query is curren...
The SAP data dictionary supports the creation of temp tables. This allows application developers to speed up the processing by temporarily storing result sets of queries in the database and later process them. The data is only kept until commit. T...
At the moment nearly all online definition changes to an object leads per default to package invalidation.So online schema evolution is very useful, but with regarding to the availability (7*24) the package invalidation isn't a great implementatio...
Do not place IBM confidential, company confidential, or personal information into any field.