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:
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
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
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.