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 a 24 hour online Db2 environment it can be difficult to complete an online REORG because the VSAM switch phase may fail, due to the activity on the tablespace being too high. The idea is to use the system monitors or a log analyzer tool to look...
Implement Inline Image Copies for COPY YES Indexes during Reorg utility operations
There appears to be expected functionality missing within DB2 Reorg Index (and Tablespace) utility operations to allow "normal" Image Copies to be taken inline for Indexes that have been defined as COPY YES similar to the inline Image Copies that ...
It should be possible to restart redirected recover in the same manner as you can restart the standard recover utility. When running redirected recover of a large group of tables, it is a waste of time to have to restart if an error is encountered...
Allow Template to populate output datasets such as PUNCHDDN to utilize PDSE's
If I use a listdef for an unload utility, I am forced to create a separate dataset for each tablespace in the listdef for PUNCHDDN's Template. I am requesting the ability to specify a PDSE in the PUNCHDDN and each tablespace would create a like na...
Hello! We have to LOAD a very large delimited file into a DB2 for zOS Table! The file comes from another organization and is deliverd to many companies! It uses ';' X'5E' as column delimiter and it is not possible to edit the file, because it is &...
Rearchitect the colgroup processing to be more granular using multiple sorts as opposed to a single sort or more intelligently avoid the colgroup sort altogether (when possible)
Looking at the job output you sent in, we can see that there are 18 colgroups specified.
Based on the current design, we have a single sort for colgroup(s).
There are 184310123 rows unloaded
The no. of the rows passed to the single
REORG SORTDATA NO should unload to shadow datasets and not unload to SYSREC
Changing DSSIZE for large table using SORTDATA NO, unloads to SYSREC. Since the volume of data is so large, SYSREC needs to go to tape. This causes the reorg to have greater elapsed time. Unloading to the shadows would greatly reduce the elapsed t...
Allow LISTDEF to be used by REPAIR where appropriate at partition level that includes a range (1:50)
Allow LISTDEF with REPAIR, such as turning off AREO* (NOAREORPENDSTAR) at partition level. This would include a from partlevel to to partlevel. This would reduce the number of REPAIRs that need to be generated.
Do not place IBM confidential, company confidential, or personal information into any field.