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.
Making the real-time stats externalization optional
The Automation Tool issues the ACCESS DATABASE(*) SPACE(*) MODE(STATS) command whenever the REALTIMESTATS option is used in an exception profile. This default behavior causes some problems:
Since the ACCESS command is issued to every DB and TS in the system, it can conflict with other processes. In our case, we observed deadlocks between the ACCESS commands and REORGs creating implicit mapping tables.
Customers can run multiple generation jobs in parallel which means the ACCESS command can be issued more than once simultaneously.
Could you consider an enhancement of making the real-time stats externalization optional? Customers should be able to decide whether they need to externalize the real-time stats thus issue the ACCESS command or they want to rely on the STATSINT zparm value in their systems and no need to issue the ACCESS command.
Do not place IBM confidential, company confidential, or personal information into any field.