This portal is to open public enhancement requests against products and services offered by the IBM Data Platform 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
When a TCB terminates while its native context has a connection to a DB2 subsystem via RRSAF, the native context for that task remains in a connected state without any means of terminating that connection except to cancel the entire address space if the current context at that time is a privately-managed context.
RRSAF will terminate the open plan and the DB2 subsystem connection only for the context that's currently active when the task terminates. The problem I'm facing is when my application switches to a privately-managed context before the subtask ends, I don't have any way to terminate the thread and close the connection, resulting in hung connections consuming system resources.
I don't have any work around for this issue. I've tried to switch to the native context using the CTXSWCH service in my subtask's ESTATE recovery routine. I also attempted to force the native context to terminate via CTXENDC. Both of those attempts failed.
The ideal solution would be for RRSAF to terminate any DB2 subsystem connections on a native context when the subtask owning that native context ends, and to terminate any open threads on that context first since no other tasks in my address space have the ability to access that native context.
| Needed By | Yesterday (Let's go already!) |
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.
Dear Christopher,
Thanks for submitting this enhancement request. Our Db2 for z/OS development team reviewed the requested enhancement and said we have considered a Db2 EOT fix for this issue is very high risk, and would have a high impact on all customers. It would require additional serialization by obtaining the AMGS_LATCH while the Db2 EOT code searched for the other Db2 agent connections on this TCB.
High Implementation Cost/Low Relative Value
Customer Impact (adversely impacts large number of clients)
Therefore, unfortunately we will not be considering this Aha! Idea.
We appreciate your input to the Db2 for z/OS development team. And we hope that you will continue to submit enhancement suggestions for improvements as customer feedback is a key component to shaping the future direction of Db2 for z/OS.
Sincerely,
The Db2 for z/OS team