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 updateson 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
Allow specification of Authid under which Federated Tables References are created
DBAs in our organisation gain SYSADM authority via a secondary authid (a RACF Group), and it is that authority that we expect to use when administering the IDAA. However when using internal Db2 security the Create Rference stored procedure to create a Federation reference does not allow you to specify under which authid the create should execute, and Db2 will not automatically check for secondary authids for DDL operations when using Internal Db2 security. This means federated tables can only be created if the DBA has access directly against their userid - which is against site standards.
We need the ability to input to the stored procedure the authid under which the reference table should be created.
This issue affects all users that need to administer Federated tables, and rely on obtaining the necessary authorities via secondary authid's, and use Internal Db2 security.
Do not place IBM confidential, company confidential, or personal information into any field.