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're using IDAA loader V 2.1 to run backups for very huge AOTs. When IDAA loader takes a backup from an IDAA AOT it uses SQL multirow fetch to transfer the data from IDAA into a z/OS sequential file. This may work fine for small AOTs. But in our environment the AOTs are very big and the SQL fetch mechanism to backup the data is not a good choice since this leads to very high CPU usage and very long elapse times. For example we determine a 70 time longer elapse time, 35 time higher CPU usage, 2.8 time higher I/O-Count and 46 time higher SU count (including zIIP-SU for the IDAA loader Backup Utility) compared to a full DSNUTILB IC for a table containing the same data in Db2 for z/OS and on IDAA. (51'239'384'238 Rows)
From a product like the IDAA loader we expect a much better backup performance. There should be another mechanism than SQL fetch to transfer the data from IDAA to z/OS. For example DSNUTILB uses direct access paths to the VSAM Cluster to read the data instead of fetching it.
Do not place IBM confidential, company confidential, or personal information into any field.