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
Start by posting 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 offering manager 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 notifications 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.
Please use the following category to raise ideas for these offerings for all environments (traditional on-premises, containers, cloud):
Cloud Pak for Multicloud Management
Cloud Pak for Network Automation - incl Orchestration and Performance Management
Cloud Pak for Watson AIOps - incl Netcool Operations Management portfolio
Edge Application Manager
IBM Observability with Instana
ITM-APM Products - incl IBM Tivoli Monitoring v6 and Application Performance Monitoring v8
Workload Automation - incl Workload Scheduler
Tivoli System Automation - inc Tivoli System Automation Application Manager (SA AM), Tivoli System Automation for Multiplatforms (SA MP)
IWS CPU usage improvement for ETT data set CLOSE events
Each IWS tracker subsystem on z/OS gets control during data set CLOSE processing in order to check, if this event is related to an ETT-defined data set (ETT = Event Triggered Tracking) in the EQQDSLST-file. If EQQDSLST contains many entries (several hundreds) this processing can consume many CPU-hours per day on a z/OS system, which are hidden, as they are attributed to the caller of the CLOSE. We have analyzed a system where a conservative estimate was at least 8 CPU-hours a day only for this IWS processing (see "use case" for details). The design of this check can and should be improved in order to save CPU-time.
Do not place IBM confidential, company confidential, or personal information into any field.