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
We have an IDAA loader job that disables the table prior to the load to IDAA. Upon successful load of # rows, Loader will end with RC = 0 and enable the table for acceleration again. If the same process is run multiple times and results in "no rows loaded" , loader will end with RC = 0 but the table is not started for acceleration. This results in queries routing to DB2 instead of being accelerated which could cause the application to experience an increase in CPU/Elapsed time. The step ends with this message "HLOU4099I 337 22:31:19.96 No data was transferred to the accelerator."
We would like to request an enhancement to loader to issue a different Return code in this scenario and consider enabling the table for acceleration when no rows are loaded.
I opened CASE TS007741616 with details of this issue that was encountered on our production IDAA system. As an interim fix we will code a step to JCL to handle when no rows loaded as this resulted in our queries not routing to IDAA.
Do not place IBM confidential, company confidential, or personal information into any field.