Skip to Main Content
Integration


This is an IBM Automation portal for Integration products. 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
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


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.


Status Not under consideration
Workspace DataPower Gateway
Created by Guest
Created on Sep 17, 2018

Expose Cursor with hold setting

Enhancement to allow override of cursor with hold settings.
Data Power as currently configured takes the default setting to add cursor with hold to every dynamic select statement issued. There is currently no way to override this as we found out through the ETR process.

Even though we issue no dynamic SQL through Data Power, this affected us in a very negative way. If you are calling stored procedures then helper procedures are invoked under the covers, in particular SQLPROCEDURECOLS. This procedure is smart enough to sense the cursor with hold setting and issue cursor with hold against the catalog. We had a thread hang and while it was hung it locked everyone out of the table. This caused every other caller of the stored procedures to fail. The fix of course is to override the cursor with hold setting which is not currently exposed.

Please consider this request and vote early and often.

Idea priority Medium
RFE ID 124855
RFE URL
RFE Product IBM DataPower Gateways