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
We are about to finish the installation of SQL Tuning Services in our sandbox environment.
What we learnt last week from Xuqin Zhao at the IBM lab is that the product currently not fully support Security mechanism 18, especially for db2_authid_R - This user ID is used to access the Db2 for z/OS subsystem where the SQL Tuning Services repository database resides.
In the AT-TLS policy in Communication server we have set Client authentication = SAF check for incoming calls to SECPORT. That means that calls from the Liberty server to the repository database in Db2 must use Security mechanism 18 which is not supported right now by the product SQL Tuning Services.
As a workaround in the sandbox environment we use a userid with non-expiring password (Security mechanism 3, non-SSL) right now. This workaround will not be acceptable when installing the product in test/dev/prod environment.
Our proposed solution is that SQL Tuning Services should support Security mechanism 18 in the communication between Liberty and repository database.
Needed By | Week |
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.