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.
Our installation has repeatedly had trouble with Db2 shutting down in a timely fashion for IPLs. We have taken dumps and sent them to IBM and IBM has stated repeatedly that the delay in shutdown involves dataset close. We set DSMAX very high and have many open datasets.
We were considering setting DSMAX to a lower number immediately prior to an IPL to allow Db2 time to close most of the datasets asynchronously, in advance, while still allowing the subsystem to remain in service until IPL-time.
The main issue with this approach is that it requires a separate ZPARM module with the different DSMAX setting to be maintained, and our Automation package to issue SET SYSPARM commands to move between DSMAX settings.
Instead, we would like to see DSMAX eligible to be set by a Db2 command, for the current subsystem-session only. This would allow us to reduce DSMAX prior to shutdown and proactively close datasets that may not be in-use, thus accelerating the actual Db2 shutdown, without actually shutting down Db2 service entirely.
This would also allow shops to increase DSMAX dynamically without modifying ZPARMs or needing access to APF libraries, should they reach a point where the current setting is leading to excessive dataset thrashing.
Do not place IBM confidential, company confidential, or personal information into any field.