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 updates on 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
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
IBM Employees should enter Ideas at https://ideas.ibm.com
See this idea on ideas.ibm.com
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.
Needed By | Quarter |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
A further thought while considering this idea...even notwithstanding the APF-library access issues associated with changing the ZPARM using SET SYSPARM RELOAD, the dynamic decrease of DSMAX presents an additional problem, in that the ZPARM setting would take effect immediately.
While this WOULD cause Db2 to start closing open datasets, it also creates a window where the subsystem is technically OVER the DSMAX limit, so if more datasets needed to be opened for a new process, they may get 00C20113 errors.
A dynamic INCREASE of DSMAX via COMMAND would likely work the same way as doing it through ZPARM. A DECREASE, however, would require Db2 to close datasets up to the 3% margin from the NEW value of DSMAX BEFORE enforcing the new limit, to avoid any outage or RESOURCE UNAVAILABLE condition.